>>>>>. It is possible to leave the report out of the build exe, but in multiuser systems I think this creqtes more problems than it solves.
>>>>>
>>>>>Marc
>>>>
>>>>PMFJI, but what sort of problems have you experienced by leaving the report.frx out of the .exe? Curious users? "File not found", errors?
>>>>
>>>>Thanks
>>>
>>>Larry,
>>>
>>>I have not tried it. But the idea to have to support a report (or multiple reports) for each stations soundd tiring enough to me to abandon the thought altogether.
>>>
>>>And PMFJI, stands for Pardon Me For J.... In, I guess. Cannot think of what that J stands for.
>>>
>>>Marc
>>
>>Marc,
>>
>>The J is for "Jumping"...
>>
>>As for the reports, you could place them on the server with the rest of the data so there's only one copy to deal with. That's what we do and I find it very easy to maintain.
>>
>>My $.02
>
>Thanks, but what happens when somebody changes the report and somebody else accesses it?
>
>Marc

Do you mean when a developer updates the report? The user gets the updated version of the report. The only requirement here is that _nobody_ has the report open while it's being updated. Of course, if the needed information is not on an existing report, we generally create a new report instead of changing an existing one.