We didn't change any SMB/SMB2 or OpLock settings recently (heck, we don't even know what it is). From what I've read, SMB1 is for old OS (Vista and older), we are using Windows 10, and we shouldn't touch any SMB2 settings. So if we didn't made any changes in SMB/SMB2 settings and our aplication ran perfectly fine for years, why should we be looking now to change it? An update from Windows?

As for FLUSH FORCE, we have a tons of INSERT/REPLACE all over the applications (we have over 400 tables), I don't see myself getting through all of them to add a FLUSH FORCE. Again, the application was running fine for years, why the sudden change in behaviour? Not just in one form, but in many of them. I can understand that FLUSH FORCE may get rid of one of our problem, ie records that do not show unless we quit and restart the application, but I can't understand how it relate to the other behaviour we see, ie records appearing in double.

I suspected the antivirus, but the problem appears even if it's disabled.

I now suspect a database/table/index corruption, but I cannot pinpoint the specific table that is causing the problem. I`ve ran a program that open each table one after the other and do a REINDEX on them with a VALIDATE DATABASE RECOVER at the end, but it didn't solve the problem.

>First stop is to check SMB/SMB2 and OpLocksettings, then flush force and doevent sprinkling
>
>>I have a very strange problem that came up in the last weeks and is happening randomly. Here's the pattern :
>>
>>- User add a new record
>>- The form refresh it's grid to show all records
>>- The new record doesn't show
>>- The user add the same record
>>- The form refresh it's grid to show all records
>>- The new record appears in double. This shoudn't be possible because the form validation prevents adding a record that already exist
>>
>>Somewhere else, a record will appears in double or will not appear at all. If I look at the data directly in the table, everything is okay (record is there and not in double).
>>
>>This bug appears in many forms, from different tables and for different users. Quitting the application and reopeining it again will resolve the display problem, but it may come back later on.
>>
>>I really don't understand what's going on here because the bug appears randomly and on forms that haven't been modified in many months/years. I tried reindexing the database and recreate some tables from scratch thinking that it may be a indexing problem, but the problem persist.
>>
>>We don't use table ou record buffering.
>>
>>I'm starting to think it may be a new incompatibility problem betwen VFP and Windows 10.
>>
>>Anyone has any ideas on how to resolve this ?
>>
>>TIA