>>>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.
>
>Sorry, I'm probably not following. I thought that you exclude reports from the project so that each user can change them at runtime. And I was wondering what happens if two users change the report that is saved commonly on the shared network harddisk.
>
>If it were not to allow users to change the report at runtime, I fail to see the advantage of excluding them from the project in the first place.
>
>Thank you for your patience. Must be somewhat elephantine on this one.
>
>Marc

No matter... there's always more than one way to do a system :) I just noticed Barbara's reply which echos the point I was trying to make. Guess that's why I'm a programmer and not a diplomat ;)

Regards

Larry