One of my users had a corrupt front end that wouldn't open.
My app is launched using a launching application (logon app). The logon app
has a button for downloading a "fresh" copy of the front end from the server
to the user's PC. I thought that this was a good idea since Access seems
susceptible to corruption.
I told the user to open the logon form and click the "Download" button, which
would then replace the corrupt front end on his PC with a clean front end
from the server. The code uses the FileCopy command.
However, this failed giving the same error message (unrecognizable database
format) as when trying to open the corrupt front end. So now I'm looking at
the "download" code and I realize that the "download" code is opening both
the front end on the server and the front end on the PC to check the version
numbers, before executing the FileCopy command. The idea is to make sure that
an old version doesn't overwrite a new version.
I just want to confirm that it was this attempt to open the corrupt front end,
in code, to check the version number that caused the error message to appear
when the user clicked on the 'Download' button (which is supposed to replace
the user's front end copy with a copy from the server). It seems like the
FileCopy command shouldn't care if the file to be overwritten is corrupt or
not. But, I can't test this as I don't have a corrupt copy of my front end
available to me.
BTW: Is there a way to corrupt a front end (.mde format) so that I can
determine exactly what caused this error to occur when my user clicked on the
'Download' button. Actually, I hope the answer is no since my biggest concern
with Access is the ease with which it corrupts.
Thank you.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200609/1