Shadow Copy Bug?!

  • Thread starter Thread starter will f
  • Start date Start date
W

will f

Here's some interesting behavior.

I develop a small app that uses a MS Access database. I had a database with
about a dozen records in it. For testing purposes, I deleted the 12-record
database Access file and replaced it with a database file with no records in
it.

When I put the new empty database file down, my app behaved as if it was the
12-record database file. What's even more interesting is that when I simply
rename the Access file, my app sees an empty database. When I rename the
Access file back to the original name, it's the 12-record database file
again.

It's as if renaming a file to a name used by a previous file (that has been
deleted), the deleted file is restored, rather than replaced by the newly
renamed file. How can this make sense? Is this a "feature" of shadow copy?"
Is Windows Vista deciding that my intention was to restore the file rather
than replace it? Also, it seems that the only way I can turn off the shadow
copy is to turn off system protection completely off.

Has anyone else encountered this, and is there a fix that doesn't require me
to turn off system restore protection completely?

Thanks.

- will f
 
In message <[email protected]> "will f"
When I put the new empty database file down, my app behaved as if it was the
12-record database file. What's even more interesting is that when I simply
rename the Access file, my app sees an empty database. When I rename the
Access file back to the original name, it's the 12-record database file
again.
Click to expand...

I've seem similar when accessing an Access file via a ODBC System
connection on a Windows 2003 server.

I found two fixes;

1) Reboot

2) Rename the file, try to access the original file (you'll get a
file-not-found error), then rename it back.
 
Back
Top