>>We actually starting opening the report as a table in an attempt to solve our original "File does not exist" error. So the error was already occuring, albeit with a different flavor. No only that but this seems to be a fairly common procedure that we have heard from various sources. Apparently, a report may not print correctly from a user's machine because the table has printer information saved on it from the developer's machine. To resolve this you make a copy of the frx table, clear out the printer information, and run the copy.
>>Any other suggestions?
>>Alex
>
>Your philosophy about removing TAG info is fine, and if you started from scratch all should be well...except that you may have some kind of path problem with your report...
>
>If you include the report in the build, don't use a path at all, just
>
>REPORT FORM myreport
>
>is all you want. Clean out the TAG stuff, save, and rebuild the exe. And careful about using the report in development, it will write the stuff right back in...

Bruce,

Alex could also write a small utility to have the reports cleaned before building the EXE. Josh Weiss published one here a few months ago.

José