Walter Meester
HoogkarspelNetherlands
General information
Category:
COM/DCOM and OLE Automation
Hi mike,
The app only sees the modified and added records when it refreshes its buffers.
You can adjust the refresh with SET REFRESH TO command (See help).
For inmediate refreshes you can also lock and unlock the tableheader (with RLOCK(0) AND UNLOCK).
Walter,
>I am using a small host app to do routine tasks like pricing when multiple users add or modify data, so the users work on a small transaction file, and ONLY the host app opens history, pricing etc.
>
>My problem is, the app doesn't seem to "see" the new records as fast as I think it should!
>
>The users "flush" after any modifications, but the host app doesn't immediately see the change despite go top/go bottom, locate for, etc. No forms or grids in use, just test for conditions & CASE in the app, users are submitting HTML or parameters to a foxisapi method.
>
>This is a WebConnect/foxisapi environment, so a lot of things are happening out of sight of my own code. It all works, but tends to take 5 to 10 seconds, which is a nuisance since the foxisapi & webconnect sessions are 'busy' waiting!
>
>typical code on the app
>
>do sleeper && win API sleep
>select transactions
>go bott
>go top
>locate for NEW
>IF FOUND()
> DO CASE
> *!* various udfs
>ENDIF
>
>thanks
>
>mike
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only