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