Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Strange concurrency problem when report is being process
Message
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Miscellaneous
Thread ID:
00448638
Message ID:
00451375
Views:
30
Barbara,

Thank you. It seems that the solution was, as you suggested, to build a cursor for the report rather than SET RELATIONS and access the master data table directly as the control table for the reporting FRX. I tried other suggested solutions, mainly to be sure that the report has it's own private data session, however, that did not solve the problem.

BTW, The problems that I mentioned to you the other evening that we were having with NT Terminal Server seems to be solved by updating VFP with service pack 3 -- it seems whoever installed VFP on the Terminal Server never installed SP3. Yikes, if it's not one thing, ...

It was nice to see you at the meeting the other evening and thank you again for your suggestions. In case you're curious, I got a hearing dog about 6 months ago and her name is Roo. She goes with me everywhere now and my clients love me bringing her around.

Joel

>Hi Joel,
>What parameters are you using for the TableUpdate() command? Is the second parameter set to force an overwrite? If it is NOT set, does that solve the problem?
>
>Can you check with GetFldState() to see if the invoice records are being changed programmatically during the report setup?
>
>Also, I've found that my reports always run more smoothly if I use only cursors for the actual data seen in the report. That way none of the 'real' tables are active while the report is being previewed and printed.
>
>Barbara
>
>
>>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
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform