What is the limit on the length of a select statement from a TCL?

I have a process that selects a number of records from a table and then displays them in a multi-select popup. After the selections are made from the popup, I then generate another select statement to grab the relevant rows from the table. This select statement is performed from codes using a PERFORM statement. I'm not sure what the breakpoint is, but if enough records are selected from the popup (immediately recreateble by using - on a large selection) the resulting select statement does not return all of the requested rows. I'm assuming this is due to a length limit of a select statement.

Any info would be appreciated.

Thanks,

Matt Sorrell

msorrell@movgal.com

Matt:

There is a limit. I've forgotten the exact number but I'd guess around 256 characters in any R/List statement - inlcuding selects.

Bryan deSilva

Improvisations

It depends on the result of sentence and the version of the software. ARev 3.12 can hold about 6 times as much output as earlier versions. Question then becomes what is output. It's not the sentence, but what R/LIST wants to do with the sentence. It's been a long time, but the increased buffer handled the format outputs for further meta reduction and cursor reduction. The heading, formatting, is indexed and other flags are stored in a structure (named C for some reason) which was only about 1000 bytes. This was pumped up to 6000 or 7000 or so in 3.12. However, due to the nature of this, a seemingly shorter statement could blow before a longer one.

It could also have to do with the internal source buffer and how it treats fields with numeric characters. If you have a field with a numeric character (ADDR1 or something) remove the number and see if that makes a difference.

akaplan@sprezzatura.com

Sprezzatura Group

View this thread on the forum...