>>>What is the best way to create/distribute new reports for existing app for remote clients? I have a client who constantly asks me to create new reports for an app I developed. When the report gets little complicated with table joins etc., I try to create local views to use in the reports. However, after I finish creating the report, I have to remotely upload the report files AND recreate the local view on the clients computer.
>>>
>>>The second step is getting laborious. Is there a better way?
>>>
>>>TIA
>>>John.
>>
>>IMHO, the better way is not to use views for reporting purposes. Views are just too bulky for this. Obviously, you don't need in buffering, etc. here. So, just create report cursor programmatically and upload new exe file to your client.
>
>Ed,
>Actually, I also don't really like to use views for reports. I would rather do it programmatically like you've said. In 2.6, I used to create all reports in a PRG file that creates SQL cursors and than calls the report form to print the actual report. I didn't have to recompile the exe since it was able to call a separate PRG file to run. Is it possible to do this in VFP? I don't want to recompile the whole app everytime I create a report.
>
>Thanks.
>John.

John,
You might let the reports excluded from the project and distribute therm apart in a seprarate directory. And also keep the reports table driven. I mean keep the information about the reports (the title that the user should see when he has to select a report and the associated report information)) in a table that you could provide or update with every new version.

If you have to use views, you might distribute them as PRG and make sure they are run at the client site at least once so the DBC gets updated. This is the sort of things that are well handled by xCase and SDT.

José