> > If anyone has encountered this problem before and found a > resolution for it, > > please post it here. As you may read from the bug thread, > the developers of > > PHP seemed to have passed this off as an IIS issue.
Hrm... haven't seen the exact error described, but gave up on mssql_* functions under Win2K, IIS5, SQL Server 2000, PHP 4.2.2 because of the fact they truncate varchar fields to 256 chars, among much other wierdness. See my "MSSQL trouble: ansi_nulls?" posts to this forum from the end of Aug. I suggest switching to odbc_* calls (hope you're nicely abstracted ;) It seems to me that many of the problems with PHP's mssql support under Windows stem from the fact they're built around dblib, which has hardly changed since Microsoft bought SQL Server from Sybase. So long as this is the case, the problems will only get worse. IMHO what PHP really needs is a complete rewrite of the functions using OLEDB. Wish I had the time and skills :( Matt
