>Thanks Tore,
>
>I think I'll take your advice, now that I know that there is a general consensus that these things are rather complicated in the data environment!
>
>Regards,
>
>Steve.

Steve;

I am another developer who does not use a data environment on a report. My experience is that using an "external data source” allows greater flexibility.

Additionally, when VFP 3 was in Beta (January 1995), I developed a number of classes for reports. I still use these today and they allow complex reports or simple reports to be created using a standard interface. Typically all that I have to do is to change a few properties on a form, write the required SQL statement, create a report and I am finished.

The basic concept is to have one form that acts as a switch board for the user. An List Box at the top of the form has the names of all the reports. An Edit Box below has details of the reports purpose. Double Click on the item of interest in the List Box or Select the OK button to be taken to a report or another form.

If you are taken to another form you can select what ever is important such as Date Range, Supplier, etc. Design the Form for the Report to give the user flexability. You can default to all or require an entry.

The guys at the Silicon Valley User Group called this, “Mini FoxFire”. When you add a Report or Form you do so through a table. I hope this makes some sense and might give you an idea or two.

When I was consulting I made a good deal of money from my Report Classes. In fact it helped to get our two children through high school and college! :)




Tom