By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,649 Members | 1,765 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,649 IT Pros & Developers. It's quick & easy.

Launching app button to replace corrupt front end

P: n/a
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

Sep 8 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a

"rdemyan via AccessMonster.com" <u6836@uweschreef in bericht news:65f6f13123a0f@uwe...

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.
Open the mde with Word (or notepad if you like)
Hit the spacebar
Save

Arno R
Sep 8 '06 #2

P: n/a
AARGGH!

That was too easy. Thanks for giving me one more thing to worry about :)

Arno R wrote:
>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.

Open the mde with Word (or notepad if you like)
Hit the spacebar
Save

Arno R
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200609/1

Sep 8 '06 #3

P: n/a
I bypassed the version code checking and was able, using the launching app
download button, to successfully download a fresh copy from the server to
replace the copy I just corrupted (using the technique suggested by Arno).

So, at least I know how to solve this problem and am making it relatively
easy for users to replace a corrupt copy of the front end. I guess that's
the best I can do, so I'll stop worrying about it.

Thanks.

rdemyan wrote:
>AARGGH!

That was too easy. Thanks for giving me one more thing to worry about :)
>>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
[quoted text clipped - 6 lines]
>>
Arno R
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200609/1

Sep 8 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.