Hi Joel!

I think the easy way - debug your program (start preview your report) and suspend your program for see "display status" command. You can see how your table use - with share or exclusive mode. I think the problem concering to database environment.

Another - clue - you must use private datasession.


>Here's the situation:
>
>A user attempts to save an invoice in my VFP 6.0 program. When any other user on another workstation is displaying a report to screen using REPORT FORM PREVIEW using tables also used in the "save invoice" process, the computer saving the invoice is unable to save the invoice. TABLEUPDATE() returns false for unsuccessful save.
>
>This is on Windows NT 4.0 workstations and server.
>
>I've traced the reports and suspended immediately before the REPORT FORM
>PREVIEW command, done a DISPLAY STATUS, and none of the tables are locked.
>
>Why does the PREVIEW feature cause TABLEUPDATE() to fail? I don't use the REPORT FORM data environment. I open and close the tables programatically and set buffering programmatically. I always have SET EXCLUSIVE OFF and use optimistic table buffering.
>
>Any help is appreciated.
>
>Joel