Re: Modify Report - failure and error message by MikeA
MikeA
Fri Sep 21 11:31:33 PDT 2007
What you might want to try doing which I have had great success with is
this:
1. First do the following to your report:
use ("MyReport.frx") exclu
replace expr with ""
It could be that some printer drivers may be buggy and do not like what they
see in this field. If the report is not compiled with the program and is
"orphaned" on the drive then when users print to their printers, VFP will
leave information in the field which may cause problems with other printers.
2. Copy the frx and frt files to their local C drive perhaps with a
different name and allow them to make changes to the report
3. Allow them to print the report from their local drive.
Mike
"Dan Freeman" <spam@microsoft.com> wrote in message
news:OSl5PZG$HHA.600@TK2MSFTNGP05.phx.gbl...
> The report writer is NOT a multi-user tool, so you could be running into
> contention. Since the tool wasn't intended for use this way, I'd expect
> results to be unpredictable.
>
> You could also be running into foxuser wackiness. It causes all sorts of
> flaky behavior.
>
> Dan
>
> Peter Rooney wrote:
>> A report is stored on the server. Various users on the network want to
>> modify the report from time to time, and run it. They Modify Report
>> from their Command Window and are in the Design view. Then they can
>> switch to the Preview view. Here is where the error comes in. Some
>> users can then switch back to the Design view to keep tweaking the
>> report, and switch back to Preview. That is, they can switch back and
>> forth between Design and Preview. Other users can switch from the
>> initial Design, and then to Preview, but when they try to switch back
>> to Design, the process crashes with an error which reads:
>> ! Cancel.
>> OK Help
>> The exclamation mark is in a yellow triangle, and the whole thing is
>> in a rectangle.
>> This is a strange message which says nothing.
>> Now this is really an insignificant error, because the users can go
>> right back from the Command Window into Modify Report. Still, it's
>> bothersome, and it makes one wonder what's going on?
>> By the way, all users have a full copy of VFP 6.0 installed on their
>> local machines.
>
>