>>
>>Now if you manage to assemble cursor like this in a series of SQL statements, then forget all this
>>because it will be obviosely much less code then this, but if calculations are to complex and
>>you don't have SQL idea that will yield resulting cursor you want, then this aproach offers quiet a bit of flexibility.
>>All complexity is basically moved from FRX (and SQL area) into procedural code within session object
>>Session object is environmentaly friendly as well, as it automatically closes all his tables when released.
>>
>>
>>BTW, Have look at
>>
>>www.report-sculptor.com
>>
>>which can help you create some very complex report layouts freely in code and/or using form objects, text files etc.
>>
>>HTH
>>Sergio
>
>Thanks Sergio. I was able to build it using a combination of SELECT followed by a SCAN loop to populate it with the additional values I couldn't get with the SELECT. The SCAN uses the UDFs so they are outside of the SELECT. Most of the calcs are removed from the frx. I agree its simpler that way.

All well that ends well :)