>>Dear All
>>
>>What is the longest SQL statement you ever used to
>>prepare report cursor(s).
>>
>>I have seen few 'elephants' here and there, now I need few of those.
>>For research purposes / with right to publish.
>>
>>Mocked up table/field names are ok, it is shear size / complexity I am after.
>
>Not mine, but I had to fix one which had a misnamed field somewhere in the middle... around line 194 of the .prg where it was. Now you made me look it up: 239 lines, 16.8 KB.

Wow!! This one would have been perfect.

Can it be mocked up / mimicked somehow with nothwind or tastrade data ?? Half of it wld have been example-grande :)


To All;

This is not about bad code or good code. Good SQL, Bad SQL , anything is fine. It is about size / complexity.

Anybody else that have such SQL 'biggies' (or piggies) can send it to me privately via email.
Will respect any wishes or demands in terms of privacy or credits.
I will probably show it just as blured bitmap. But it has to look realistic.

TIA