Steffen Heil wrote:

>>As previously noted, this seems to be a Windows "display" issue.
>
> Have you read my post and have you tried pushing F5 in windows explorer
> while writing to the database?

Having lived with this problem since Win98 and probably before. BDE had
the option to 'purge to disk' - it never worked. Windows would cache the
data in memory what ever you did. Later versions of windows do things
differently, but what you SEE in 'explorer' is what windows want's you
to see, it is not what is actually happening on the disk, but rather
what windows view of what the disk SHOULD be like - if you save
everything it is currently caching. Pull the plug on a long running
dBase BDE application, and the data was lost, close the application,
everything gets saved. CODEBASE addressed a number of the problems in
the same way as 'Forced Write', by bypassing windows, and pushing each
write direct to the disk. You could pull the power on a Codebase dBase
application and only lose the current record changes.
The whole problem is simply windows was never designed to be a server
operating system, and until it addresses that problem, we need to
prevent it from getting in the way by 'Forced Write' of data to the
disk, or using a 'safer' OS, which actually writes the cache with some
level of urgency ;)

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services