Large Scale Corruption!

TKnight

Registered User.
Local time
Today, 12:59
Joined
Jan 28, 2003
Messages
181
Hi all, apologies for the long post but this is a long nightmare!

Using A2k on Win2k...Due to roll out a DB today, just made my final tweaks and decided to compact/backup as have done many times before. It's not a split DB but it is secure so I copied the mdw onto my desktop and accessed it using a special compact shortcut which points to the desktop copy DB not the one on the network. When I compacted though Access went about it's business for a while and then threw up the dreaded "Network connection may be Lost" error message (roughly translates as "your database is nicely corrupt now") which I have had in the past when I tried to compact on the network. I've never had this error before compacting locally but anyway I tried again and same error message. I tried opening some forms and stuff and sure enought the DB was corrupt. No probs I thought, I can just go back to the original and start the process again. I used the normal shorcut to open the original DB just to check everything was ok and the same error message appeared with same problems. Minor panic ensued and I thought i'd got the shortcuts mixed up or something... I hadn't, Both DB's were affected.

Next option. Create a new DB and import all the objects. I did that and re-set all the permissions and the "Network Connection Lost" message dissapeared but some really strange things were happening. Forms opened but the buttons on them would do nothing. Then the forms Close button didn't work and the database wouldn't close.

I forced my way out of the DB and re-started my machine. Couldn't even log in to windows. Now at another machine and can log in to windows but DB is still having same problems. My instict tells me that the problem is something to do with the workgroup file becuase how else could compacting a copy corrupt the original? The only common link is the mdw.

Should I re-create the mdw and then try opening/importing the DB objects again? Or is there any way I can un-secure the DB and then re-secure it later?

Any thoughts would be much appreciated.

Thanks, Tom
 
Thanks for the help...

I have the KB article and it does seem like the problem becuase I did import a module from another database a few minutes before I closed to do the compact. I can't seem to follow it's resolution though?

It says to open the form in design view and save the code behind the form as a text file. I can't do that because it won't let me open the VB editor window. Is there any other way I can get the code out?

Thanks, Tom
 
Hi, the article says you need to be on a computer without the version of Vbe6.dll that is mentioned, for the solution to work.

Do you have a higher version of Access on another machine?
 
Yeah I checked the version of the dll on the machine I was working on and it was different to the problem dll mentioned in the KB.

I have sorted it now though. I couldn't view the code to export it so I just removed all the form, report and standalone modules and re-saved the objects. Then I opened up a test Db that had up-to date code but old queries and tables and cut-n-paste from there. Think I have everything back to normal now but am worried i'm going to face a problem i've already fixed in the future.

Gotta love those MS quirks!

Thanks for your help. If I didn't get that KB article i definitely wouldn't have been able to sort it,

Tom
 

Users who are viewing this thread

Back
Top Bottom