We're not modifying the report that is included in the .EXE. We do a USE on the report file that is included in the .EXE, then do an SQL-Select into a temporary table on disk, then modify that temporary table. This temporary table (report) is what is used by the REPORT FORM command.

Before using this method, we weren't clearing out the TAG and TAG2 fields at all, so we just used the REPORT FORM command with the report that is included in the .EXE. We still would get the "File does not exist" error from time to time when the REPORT FORM couldn't find the report file.

Thanks,
Jonathan

>>The problem we are seeing now is that the code appears to be bombing when it tries to open the original report as a table with a "File does not exist error". This seems odd, since the report is included in the .EXE.
>>
>
>I don't see how this could ever work for reports that are included in the dbc- if it is included, then it doesn't exist. Its definition is embedded in the exe. You can't modify files that are included in the exe...