Hi John,

Thanks for taking the time to reply. Based upon your situation being fairly close to my client's, I went ahead with the change. I closed the files after every check of the table and the new records were detected it would seem just about immediately after being submitted (at least no 20 second delay). I also turned off write-caching (although this did not seem to do much on it's own - I tried that first).

Thanks a lot.
Albert

>Albert,
>I have an app that polls for new, incoming data sent via FTP from salesperson's laptops to a MS server. All the data are in VFP tables. One EXE program looks for new incomming zip files, moves them to another folder and updates a table with the new jobs in the queue. Another, totally seperate, EXE app runs those jobs and creates the customer sales orders in the main system.
>
>I found that when the first EXE updated the queue tables the main EXE instance would not see it for over 20 seconds. I tried everything including FLUSH but nothing worked. Then I tried closing the tables each time before the update or query and the problem was instantly fixed. As far as performance goes there was no difference. Of course I am using record locking and the close/open has no problems with it.
>
>If nothing else I strongly suggest you try it. If you are using all SQL for your data work, which you should be, it should be a snap to add some code before each SQL to close the open data tables.
>
>John.
>
>
>>Hi John,
>>
>>Way back when I first wrote this for the client (ca. 2002), I worried about having the tables opened and closed so much (the polling takes place every 3 seconds). Figured it would cause its own problems. Questions:
>>
>>1) do you think opening/closing every 3 seconds will cause a problem?
>>2) can you describe the situation you applied this to and how it solved it
>>
>>Thanks,
>>Albert
>>
>>>Albert,
>>>been there done that. If the DBFs and the query program are on the same server then you will not pick up the changes from the other side right away. I fixed the problem by closing the tables before each query. Yea, FLUSH is supposed to do that but not always and closing and reopening the tables is instantaneous.
>>>HTH
>>>
>>>John