Cursor Cannot be Modified Because it contains an unsaved record

fmoore0001
fmoore0001 used Ask the Experts™
on
Of thousands of clients with our software installed, I am getting an error with ONE client I cannot account for.

In their database they recently started getting this error:

"Cursor Cannot be Modified Because it contains an unsaved record"

They have been using our software for months, and just suddenly this error started occuring.

NO other client has reported this problem.  Any ideas?

Frank
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
According to Microsoft:


Visual FoxPro 9.0 SP2
Cursor cannot be modified because it contains an unsaved record (Error 2072)

This error typically occurs when a record in a cursor is modified in a grid or Browse window and is not saved before moving to another record.

Any code that modifies the cursor should ensure that all modifications are saved before moving the record pointer.
Olaf DoschkeSoftware Developer
Commented:
Help says about this error (number 2072):
This error typically occurs when a record in a cursor is modified in a grid or Browse window and is not saved before moving to another record.
This is misleading, if the table or cursor is not row buffered.

Also see http://www.foxite.com/archives/error-2072cursor-cant-be-modified-0000091423.htm

Bye, Olaf.
Microsoft should also explain why this happens on one of 1000 installations...

I would guess this is impossible to fix in reasonable amount of time. The easiest fix is to reindex (and possibly pack) all tables. The second level means to reinstall the whole machine otherwise you would need to test on site in development VFP version or dramatically enhance application dump when this error occurs.

Author

Commented:
This problem was related to the same client I had with the Weird Netword problems.  When I did a table repair (the INDEX ON routine did not fix it.  I have a 3rd party APP I include to repair damaged DBF files) the last of the problems disappeared.  I have a feeling it was a circle- network settings damaged the table, then I fixed the network settings the table was already damaged.   That was four days of panicked work with a screaming client!  Thanks for your help.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial