2005 Dec 16 8:26 AM
Hello all.
I'm getting a pretty serious error with the command SELECT. I use native SQL to get some data on an external database. I use it in order to get a field "image" in a mssql table.
The code :
data tempbyte type xstring.
EXEC SQL.
SELECT Filename, Filesize, Doc INTO :filetemp, :file_length,
:tempbyte FROM Docs;
ENDEXEC.
For small file around 30ko it's working fine. For file more than 100 ko it crashs severely.
Another thing quite surprising it's that the insert of a big file in the external database go smoothly.
data tempfile type xstring.
EXEC SQL.
INSERT INTO Docs(Filename, Filesize, Doc)
VALUES ( :temps, :wf_file_length, :tempfile);
Commit;
ENDEXEC.
Is there some limitation on xstring data?
When i execute the select statement a message popup "Work process re-started, session terminated". When i loof in the dump the probelem seem to come from the sqloledb.dll.
Is someone alredy had a similar problem? Many thanks for help
Hello all.
I'm getting a pretty serious error with the command SELECT. I use native SQL to get some data on an external database. I use it in order to get a field "image" in a mssql table.
The code :
data tempbyte type xstring.
EXEC SQL.
SELECT Filename, Filesize, Doc INTO :filetemp, :file_length,
:tempbyte FROM Docs;
ENDEXEC.
For small file around 30ko it's working fine. For file more than 100 ko it crashs severely.
Another thing quite surprising it's that the insert of a big file in the external database go smoothly.
data tempfile type xstring.
EXEC SQL.
INSERT INTO Docs(Filename, Filesize, Doc)
VALUES ( :temps, :wf_file_length, :tempfile);
Commit;
ENDEXEC.
Is there some limitation on xstring data?
When i execute the select statement a message popup "Work process re-started, session terminated". When i loof in the dump the probelem seem to come from the sqloledb.dll.
Is someone alredy had a similar problem? Many thanks for help
2005 Dec 16 9:08 AM
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |