Would a maximum POST size be affected by named pipes-TCP/IP change?

The techs at my site's host and I are still struggling to solve a problem with a database insert form that stopped working. (WinNT, IIS4, PHP3) After many, many test posts I discovered that it was a matter of the size of the SQL string being submitted. One character longer and we'd get an error, one shorter and the article would insert into the database. If it was too long we'd get no error messages, if it was just a few characters over the fail point we'd get an "Unclosed quotation mark before the character string" error message even though the SQL string was formatted correctly. Obviously something was truncating the POST string and therefore omitting the closing punctutation. The odd thing is that we have successfully submitted much larger articles than the one we're having problems with now in the past. The only thing I can think of is that this started happening when they changed our ODBC connection from named pipes to TCP/IP. Can anyone think of any quirk, bug, or voodoo that would cause what appears to be a limit on the size of the HTTP POST string? Thanks. My head's sore from all the banging it's doing on the desk. -- Ian Evans