Hi there,
We are using the Actual ODBC driver to interact with a SQL Server 7.0
database. Nearly everything was working fine, until we started
inserting large chunks of text into the database which would crash the
application. We were originally working with varchar(8000) columns, but
moved them to text columns with the same results. Concerned that it was
a unicode issue, I tested by sending some straight ascii text with a
char length of 10000, and brought down the entire sql server! I can use
other tools to do the same thing, so I presume it is an issue with the
ODBC driver but would appreciate any other thoughts on the matter.
Specific questions:
1. Has anyone experienced an issue like this with the Actual ODBC
driver (or any other for that matter)? Actual uses freetds behind the
scenes, so could it be an issue with freetds?
2. Has anyone experienced an issue like this with SQL Server 7.0
3. Is there anything else we should be investigating?
Thanks,
Stuart
=================================
Stuart Parker // Web Objectives Pty Ltd
stuart at webobjectives dot com dot au
http://www.webobjectives.com.au
+612 9499 3166 // 0421 359 297
33 Ridge St, Gordon, NSW, Australia
=================================
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|