>on another topic, have you ever developed a
>"report catalogue" type form where there is a list
>of reports in a list box of some sort, choices to
>sort those reports and select ranges (ie. sort by
>customer name, select A-M), and output to
>screen,printer, disk... something simple, robust
>and easily implemented and understood by users.
>FoxFire, etc are big, complex beasts (although I
>will probably implement them for power users), but
>I want something small, quick and just a few
>options...
>
>One of the other options would be to have "summary
>or detail" and then use the SUMMARY option on the
>REPORT command...

Jim

The approach I try to take with reports is to do as much as I can before the report even loads. I usually accomplish this by running one or more SQls to cursors & read from the cursors in the report. The Fox reports are very limited as far as what you can do so the object is to 'cheat' as much as you can! <s>

What you mention above is best done by mastering SQL. I see nothing wrong with your first approach. Just have all the buttons & other 'doo dads' create the SQL you need.

BTW, yes I do live on the UT -- I gave up on CIS & the like so this is where I take my 'breaks'.

Tom