>Another possible try is that you can check the buffermodeoveride propery of the cursor in the data environment and set it to 5. and set reporcess to automatic.

This suggestion doesn't seem to fix this problem...

The easy to reproduce scenario would be:

1) One user has a file under unclosed transaction

2) Another user tries to update the same file.

You will see this message and the only way out is either:
1) Close transaction for the first user
2) Kill VFP - users do it a lot...