Thanx a million times David! I just tested your suggestion and it works just fine! (But I put all the code in the sp's instead) I had a look at the odbtp.sourceforge.net site, and I realized that this would take a time to transfer the current code I built based on the mssql ext. With your suggestion, I can easy alter a couple of stored procedures and it will the work out just fine with. Thanks again for saving me much time here! On Tue, 2004-04-06 at 15:28, David Felton wrote: > Yes there is this workaround: > if you run this query first > @mssql_query( "SET TEXTSIZE 1024000", $db); > > then when you want to retrieve a field of type ntext or whatever use the > following syntax in your sql: > SELECT CAST(fieldname AS TEXT) ... > > -----Original Message----- > From: Svensson, B.A.T. (HKG) [mailto:B.A.T.Svensson@xxxxxxx] > Sent: 06 April 2004 2:23 > To: php-windows@xxxxxxxxxxxxx > Subject: Re: Re: ODBC or MS SQL DLL? WAS: Using PHP on Server > 2003... > > > On Tue, 2004-04-06 at 14:52, Robert Twitty wrote: > > The best extension for accessing MS SQL Server is the odbtp extension at > > http://odbtp.sourceforge.net. The odbc and mssql extensions both have > > limitations when used with SQL Server 2000. > > > > mssql ext: > > - Uses the obsolete, unsupported and non thread safe DB-Library. > > - Does not support varchar(>255), nvarchar and ntext fields. > > Just tried this out, and indeed the driver just returned a string > with lenght 255 when I in fact returned a string of 1000 chars. > > That is a sever problem for me, since I frequently needs to > return strings much longer than 255 characters. Bad, bad, bad... > > Is there absolutely now way to change this? > > > - Cannot use FOR XML clause in SQL. > > > > odbc ext: > > - Uses ODBC 2 instead of ODBC 3. > > - Does not provide support for stored procedures. > > - Does not support nvarchar and ntext fields. > > I don't uses ODBC for other reasons: Is imply does not trust > it reliability to transport large data sets - sometimes ODBC > drops rows without any particular reason and without raising > an error - and as such fault can't naturally not be encountered. > > > > The odbtp extension is considerably faster than the odbc extension, and is > > just as fast as the mssql extension. It also provides support for all of > > the mssql_* functions, which means it can be used as a "seemless" > > replacement for the mssql extension. And, unlike the odbc and mssql > > extensions, the behaviour of the odbtp extension is the same on Linux/UNIX > > platforms. > > I'll have a look at this. > > Anyhow, thanks for your feedback, it was very helpfully. > > -- > PHP Windows Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses. > ********************************************************************** -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
