TD 6.2 SP2 Up2 SQL Problem Text Columns SQL Server

[MSchmidt]

Yesterday we made an update from SP2 Upd 1 to SP2 Upd2

After starting our main application we've got a SQL Error message without any description.

After some hours we've found the reason why:

Inside the SQL select statement there were 3 columns defined as text on the SQL Server
If we reduce the SQL select to only 1 text colum the SQL is working.


So I've made a test case.

inside the zip-file there is a SQL script file for the building of a table which is used in the test case.

In the test case you can see the Problem under the pink coloured push Buttons.
the green coloured Buttons are workarrounds.

If we make a SQL-update in the testcase, the application crashes.

The Workarounds are not a solution for us, cause we are not able to find all locations in our code, where more than one text column are used in a SQL Select

Conclusion:
SQL Select with more than 1 Text column is not possible any more.
The application crashes (!) in case of a SQL update with a text column inside.

We are not able to work with this version of TD!

I think Gupta should make an EMP for this Problem

Thank you
M.Schmidt

[lorenzf]

Unfortunatly we have the same problem:
SQL Error 20054, no error text.

kind regards
franz

[VEspinal]

Hi All:

The reprocase that you've sent is working for me.

I took the liberty to add a small function to clear the multines and the datafield every time you press any pushbutton in order to have a better view of the information.

I was able to click the 4 pushbuttons with no crashes. Unless there is something else that I something that I am missing.

Please see attached video.

Thanks

Best Regards,
Victor Espinal

[MSchmidt]

thank you for testing and for the quick Response

I checked my SQL.ini

There was a high value for the longbuffer keyword in section of [odbcrtr]


dealing with this value SQL is working!!!!!!!!!

We set the value higher than the standard value 32000 cause we are saving files in the database.

With a value of 55000000 the SQL is working fine

But with 755000000 the SQL doesn't work.

So I think it would be a big help for all of us, to have the limitations of the value of longbuffer.

In the help file I've found only this:
longbuffer Keyword in SQL.INI File

If you connect natively to Oracle, Informix, or Sybase System 10 and System 11, the longbuffer keyword in the SQL.INI file specifies the maximum number of bytes of long data type columns to read from or write to the database, and truncates excess bytes.


Maybe the development of Gupta can give us a statement to the longbuffer value and it's limitations.

Thank you
M.Schmidt

[ianrudge]

+1

[MSchmidt]

after more than 2 months, I ask again about the function and the limits of the LONGBUFFER value
in SQL.ini file

thank you

M.Schmidt

[H3PO4]

+1

[frevelundfey]

Hi,

this is not the answer to you question but maybe it's helpful:

Besides setting longbuffer in SQL.ini which affects all cursors you connect to the db
you can set the longbuffer-size per cursor programmatically:
Call SqlSetParameterAll( hSql, DBP_LongBuffer, nDesiredBufferSize, '', TRUE )
We use that when we have to fetch large blobs or texts from db.

Regards Thomas

[PeterFr]

Hello,

I tried to set it with:
Call SqlSetParameterAll( hSql, DBP_LongBuffer, nDesiredBufferSize, '', TRUE )
but DBP_LONGBUFFER or DBP_LongBuffer is not a valid constant (got a compile error).
I found it in the help documentation but it seem it's not a valid constant. Strange.
Using TD63SP2.
Thx!

[frevelundfey]

Hi Peter,
you are right. This constant is not available in Gupta Runtime.
But in help I found it and defined it in my .apt:
Number: DBP_LongBuffer = 5112 ! Konstante - Quelle: Gupta-Help

Regards Thomas

[PeterFr]

Thanks Thomas!