Michael, there was a huge debate about the FLUSH command in thread Flush why not flush? Thread #748117 Message #748117. Basically the FLUSH command "asks" the OS to commit changes to disk but that may or may not happen depending on a number of factors beyond the control of VFP e.g. disk write caching.

The thread highlights various options and strategies that might help you but I would say issuing a FLUSH after each save is going to really slow your app down without necessarily giving you the protection you want.



>I just lost 30 records I was adding in an application.
>I use row buffering on all tables.
>Ex: =CursorSetProp("buffering",3,"company")
>All tables are opened when the app starts. None are opened in the DE.
>Every new record I added was lost when my laptop locked up and I had to reboot.
>Existing records I changed were ok for some reason??? I had been adding records over a 2 hour period.
>Since this has never happened to me before should I now issue a flush after
>each save?
>This is how I saved records: =Tableupdate(.T.,.T.,"company")
>
>TIA