I am starting a new thread on the problem of a string being truncated to 256 chars when used in an 'opendataset' method. I really need to find out how to get a string longer than 256 to be processed. I have a database DB, a recordset RS and a string sSQL. sSQL is assigned from a multi-line text box. I then execute a command db.openrecordset(sSQL). If the len(sSQL) <= 256, then the query is executed correctly.....if the len(sSQL) > 256, then I get various errors telling me that I have an invalid SQL statement. In the error message, it shows the sql statement that it thinks I sent it....however, it is always truncated after character 256. Maybe this is truncated sql statement is due to the MsgBox statement used to show the error.....but in all cases, if the len(sSQL) > 256, then I get errors......What am I missing.....surely, 256 characters is not a limit on a string for an SQL statement. Any help would make me crazy with happiness!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
256 byte limit on SQL strings 1
- Thread starter TomSnider
- Start date
-
1
- #2
Best bet? I'd use ADO if I were you...
Go to Project->References and include Microsoft ActiveX Data Objects 2.x library.
to retrieve a recordset:
dim cnnConnection as new adodb.Connection
dim rstRecordset as new adodb.Recordset
cnnConnection.ConnectionString = "<connectionstring>"
cnnConnection.Open
rstRecordset.Open "Sql Statement Line 1 " & _
"Sql Statement line 2 " & _
"Sql Statement line 3 ", cnnConnection
I've used HUGE Sql statements w/ ADO and never had a problem.. It tends to be a lot better than DAO anyways.
Just a suggestion.
--NipsMG
Go to Project->References and include Microsoft ActiveX Data Objects 2.x library.
to retrieve a recordset:
dim cnnConnection as new adodb.Connection
dim rstRecordset as new adodb.Recordset
cnnConnection.ConnectionString = "<connectionstring>"
cnnConnection.Open
rstRecordset.Open "Sql Statement Line 1 " & _
"Sql Statement line 2 " & _
"Sql Statement line 3 ", cnnConnection
I've used HUGE Sql statements w/ ADO and never had a problem.. It tends to be a lot better than DAO anyways.
Just a suggestion.
--NipsMG
- Thread starter
- #3
Well,
An equivalent or higher version of MDAC must be installed on the target machine... However.. If you use the Package and Deployment wizard in Programs-> Microsoft Visual Studio 6.0-> icrosoft Visual Studio 6.0 Tools folder, you can create a setup program which will automically include AND install the required version of Data Access Components on the target computer during installation..
If you don't have the Package and Deployment wizard on your computer, just download the latest version of MDAC from Microsoft, and include it with the software, installing it on target machines before your program is run.
Hope this answers your question.
NipsMG
An equivalent or higher version of MDAC must be installed on the target machine... However.. If you use the Package and Deployment wizard in Programs-> Microsoft Visual Studio 6.0-> icrosoft Visual Studio 6.0 Tools folder, you can create a setup program which will automically include AND install the required version of Data Access Components on the target computer during installation..
If you don't have the Package and Deployment wizard on your computer, just download the latest version of MDAC from Microsoft, and include it with the software, installing it on target machines before your program is run.
Hope this answers your question.
NipsMG
- Thread starter
- #5
- Status
