>>I'm astonished to find in VFP 3 the old problem of report files being opened exclusively while in use.
>>
>>This means for multiuser printing I have to copy the report file, print from the copy, and then erase it.
>>
>>Is it just me? Or is this old feature really still in 3.0?
>
>It looks like that.
>
>>This has advantages too, because I can store the report files in memo fields in a system table embedded in the .APP and then copy the reports out of there to the runtime directory.
>
>You can do the same thing even if report files wouldn't be opened exclusively, isn't it? So, no advantage.
>
>>SO if the client developers decide to edit the reports and mess it up - there is a way of regenerating the originals without hacving to go on-site.
>
>I think that if the report files are included in the project, they will be also included in the app/exe. Which means the user can not modify the originals anyway.
>
>Vlad

Of course, you can mark reports "Exclude" as you do tables, so the user CAN change them. This is great for reasonably knowledgeably end-users.

Barbara