Hi all,

> BTW, I just came across some more Windows Weirdness whilst playing
> with this on a notebook with WinXP Home:
>
> I opened a db, made and committed changes, kept the db open, and
> then made a filesystem copy from the Explorer. To my surprise, the
> copy had the same (old) timestamp as the original in the Explorer.
>
> I thought maybe Forced Writes was off (although I never turn that
> off) so I opened the copy and... yes sir! The copy contained the
> fresh changes I made in the original, although it still had the
> original's pre-modification timestamp!
>
> IIRC Win2K gives the copy the correct - current - timestamp.

Well, I did *not* remember correctly: Win2K has the same quirk. Must
be a generic Windows "feature", then ;-)

Grtz,
Paul