Hi Kenneth,

Something is definetely wrong with this SQL. I've tried to format it a little bit, but gave up in the middle. Can you tell, what exactly it is supposed to do and how does it get constructed? You can also download my Statistics form File # 9684 from Downloads section here, it would allow you to display the SQL and print it.

BTW, my friend lived in Boulder for a few years...

>Hi Folks,
>
>Larry Rix here from Platts. I ran into an issue tonight that I can find references to here on the UT, but not an apparent solution. Perhaps you folks can assist.
>
>I have a SQL statement that is built like:
>
>

>LOCAL ;
>   lc_sql as String
>
>...
>
>lc_sql = ;
>   " SELECT " + ;
>   ...
>
>...
>
>&lc_sql
>

>
< skip >

>When the macro is executed, I get an error message (1812) that says that the object code is too large to execute. I have checked the SQL statement and it is 2588 characters in length (way smaller than the 8192 in the system limits). Here is the SQL for those of you that might like to see:
>
>Has only ever seen anything where the SQL engine complains about length of the object code, but that the real issue is something else in how the SQL is constructed? I am at a total loss at this point.
>
>I apologize that the SQL is not formatted. You are seeing it above as it was copied from the code. I used an

ASSERT (( .f. )) MESSAGE "debug: What is the SQL?"

to stop and grab the SQL with a

_CLIPTEXT = lc_sql

.
>
>Thanks so much for your assistance.
>
>
>Cheers,
>
>Larry Rix
>Platts