Hi Craig,

Did some testing and FLUSH on it's own did not help but FLUSH...FORCE did. Will put into production overnight and see if it helps tomorrow.

Thanks again.
Albert

>Make sure the code does a FLUSH after writing, This forces the OS to flush its buffers.
>
>
>>Hi all,
>>
>>Wondering if anyone can either confirm this problem and/or suggest a fix (even confirming it would be nice):
>>
>>- desktop app, mostly free tables
>>- uses and posts from local views
>>
>>Problem: users enter a quote in a form where this is the parent record and child records (same form); under Windows 10, when users save out the data, if they go back into the form, the child records do not show up right away. This only happens under Win10. Here is what I know and have tested:
>>
>>- suggested technique for the framework I am using is to issue a quick RLOCK() on the affected tables this is supposed to force VFP to re-read the tables (in their notes, this is the fix if a user cannot see data posted by another user on the network - but the problem is that the user cannot see the data they themselves have just posted)
>>
>>- I have turned off a feature in the app which upon app startup, opens tables in the default data session of the app *and keeps them open* - this feature is in the app to speed up subsequent openings. I have turned this off so that hopefully, when the user re-opens the form they have worked on, it forces VFP to re-read the table.
>>
>>Anyone else seen this behaviour?
>>
>>Albert