Mark:

A good idea but no dice! All of the reports are correctly identified and in their appropriate places. Since this application is only used heavily every couple of years, I decided to include the reports in the app. They rely heavily on SQL cursors built in prep for the reports and the reports themselves use functions from the main program to do some of their internal processing. I've never been able to get exactly what I want from the Foxpro report builder anyway, it seems I always have to do something outside the report to display exactly the information I need to see.

I did find an interesting aside to this issue though. The client is running Visual Fox 5.0 and that is what I developed in. I made a change in Visual Fox 6.0, as that is what I have on my notebook, and compiled the changes. That's when the problem occurred initially. I have since recompiled on 5.0 with a couple of the client machines and still have the problem. If I compile in Fox 6.0 and include the .dll files for the client, it works OK. None of the changes I made should be foreign to 5.0, so why won't it work there?

Thanks for your help.
Tom.

>To summarize, your problem is with a relation established in the DE of a report. All runs OK from the debugger or interactively but not from an APP or EXE you have built.
>
>If so, I would think you have a rogue copy of the report that is included in your project. Modify the project and click on that item in the report list. Look at the description and path in the bottom box of the PM. If you do not have this activated, right click on the PM titlebar and click the Display Description/Path option. You may need to remove that report from the project and add back the correct version of that report.
>
>In general, I always exclude reports and provide them in their own subdirectory. That way, when the users inevitably want a change in a report, I provide a new copy instead of a new compiled app.