Michael, basically FLUSH will not guarantee that the data is written to the disk while at the same time issuing a FLUSH after every edit is going to slow down the app. You can use a BEGIN TRANSACTION...END TRANSACTION but even that will not guarantee that the data gets written because of O/S disk write cache settings.

The time period over which the data was added is not necessarily that important per se as its more the volume of data that will determine when cache's are written and cleared.

I would first try to understand why the app hung after 2 hours. This may lead you to understanding why some data was saved while other data was lost. In addition to FLUSH you can also have a look at the SYS(1104) function.



>I just read the whole thread. Still not sure what to do????.
>This was a stand alone app on a win95 notebook
>There are no begin transaction ... commands
>The app is written as multi user for the future but only one person uses it.
>I just can't understand how 30+ records could be lost over a two hour period?
>There are two tables: employee and tests. 30 tests were added for existing employees and 6 new employees were added with 6 tests. (36 tests added) When a record is added to the test table data is also written to the employee table.
>
>What happened: The PC locked up after 2 hours of adding records. After a cold boot, every new test disappeared, the 6 new employees remained but the records were unreadable. The "funny" part: The 30 existing employee records all had the correct updated information.