[AccessD] Windows 7 Running Cached Old Version Of MDB

Hi Andy

As for you losing your mind - I was of the opinion this was an established fact ages ago <snigger> (love ya mate).

As for this copying issue. In one version of windows or another they introduced the 'feature', where....copying a file with a view to overwrite an existing file of the same name, a popup is presented to users asking if they wanted to overwrite the existing filename or make a copy of the file name.

It's from this time onwards where I had some nightmare scenarios at client's  offices where I would copy what I thought were latest versions from my USB stick, into a client's environment. Only to discover I had copied some earlier version. Frustrating and perplexing.

It seemed this new windows overwrite "feature' was not working as advertised. Took ages for me to find out it was this issue (Similar to yours).

My only solution was to rename the original target file so there was no overwrite possibilities - And then copy the latest version with the desired file name.

Thus 'kinda' guaranteeing it was a new file drop and not a copy or an overwrite - make sense?

I got hit by this a few years ago BTW - I think I raised it here back then - can't recall the response - Sorry

All the best to the fam.

D


-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey
Sent: Monday, 7 January 2013 10:37 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Windows 7 Running Cached Old Version Of MDB

I thought I'd truly lost it this time.


Running our main MDB one machine was giving the message that it was running an out-of-date version. This uses a home-spun routine and triggers a new version to copy down from the network. But the error message persisted. So I manually did the copy and it still happened. I looked at the file on the server and it was the latest version. I copied it to the folder on C:, looked at it there and it was the old version. What the......?????? I copied the version from the server to another folder (C:\Temp) and that ran fine. Copied from C:\Temp to the file's normal home on C: and got the error message again! Bizarre. Here’s the best….I deleted the MDB and ran it from the Windows icon that the users use, waiting for the Windows error that it was trying to run a non-existent file. But no, it still ran and gave the error. So now it’s running a file which doesn’t exist.
Now beginning to doubt the evidence of my own eyes. Flushed recycle bin, deleted temporary files, switched pc off and back on. No change. Renamed the MDB and it ran fine. Renamed it back to its original name and got the error. Logged on as different user and the same file ran fine. Decided I’d lost it and went and sat in a darkened room going la, la, la, la.

By now it was dawning on me that Windows had to be caching the old MDB and running that so I Googled "windows 7 running cached version" and found the solution. Go to

C:\Users\this user\AppData\Local\VirtualStore

and there’s the cached copy. Delete that and all is well.

Who knew? No doubt all of you, but it's a new one on me. I'm posting this to help anyone else who has this happen but also to ask if there is a way to prevent it as it totally interferes with any version management you might have.
Anyone got the answer?

Cheers

Andy

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com