Hi Hilmar

I gave up using Flush because it was taking 1.25 seconds per record in VFP 7.0 on a Dell PIII-450mhz Win2k 100meg Ethernet network. So if I updated 100 records it took over two minutes. However, removing the Flush the update was done almost instantly.

I understand the risks but the users were complaining about the slow speed of the application. So I would only use the flush command in some very critical sections.

Simon

>>Hi,
>>After a long thread of dicussion, what is the conclusion on flushing data?
>>1. Turn Off "Server's" Hard Disk Write Cache?
>>2. Use API to flush all updated files?
>>Or.. ???
>>
>>Thank you
>
>Yes, right, the previous thread changed to aspects over what MS should have or should not have done - and over which we have no control right now.
>
>My personal opinion is that if you turn the hard disk write cache off (and religiously use FLUSH after each change) you should be quite safe.