By the way I think... by Ken Levi you are referencing MicroSoft KenLevi. Hmmmmmmm..........
The problem could be because of buffers, and the table appears to be updated, but the record is lost. In technic this is possible, if the write behind is enabled and the records are in the buffer. If the computer reboots, the buffer is lost. OR even a DLL error or some such funny error from OS can make the buffer to loose your data.
The resolution is .. after every write into tables, get into a habit of issuing the command.. FLUSH. This will ensure that everything is written to disk.
VFP5.0
I have noticed the same issue. On occasion, without any known sequence of keypress or other specific known user activity, one or in some cases many records were lost completely. Anytime the program is started, I check and on error, (index does not match table), automatically delete and recreate all associated index files but the records are indeed gone and must be re-entered by user. I have not tried Ramani's suggestion of using FLUSH but certainly will look into it. The real problem I encountered was in not being able to reproduce the 'deleting records' event here in the development environment.
Where should I put the FLUSH? Behind every table update?
Thanks for the information.
George
PS The user has reported other 'strange' events with the OS sometimes locking up etc. Suspected that may have been related but didn't know how to relate the two things.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.