Corrupt .mdb ??

  • Thread starter Thread starter Tcs
  • Start date Start date
T

Tcs

Here's a really weird thing Started just this morning. Access 2k .mdb, about
667mb, on my XP sp1 box, I'm the only user.

When I right click on a query, then select "Design view", Access *immediately*
closes. Wham, bam. No nothing. Just...GONE. I can get back in it okay. But
this problem won't go away, so far. And yes, I've *already* been running
"Compact & Repair". (I've been pulling a bunch of data off our AS/400, and
deleting and recreating several tables. I want to make sure I don't hit that
"magic" 2gb limit, so I've been running C&R several times a day for the past
couple days.)

I've gone thru the series of queries I've been working on for the last several
days. It seems that it's only one query that is the problem. Just to be sure,
I've taken a copy of my .mdb from last night (before this problem started), and
exported my queries from the current one with the problem into last nights.
Well, all the series *except* the problem one of course.

Has anyone seen anything like this? Any idea what the deal is? Think my
solution is sufficient?

Thanks in advance,

Tom
 
It could be a corruption problem or a problem with that query. If there is a
corruption problem, then exporting objects from it to yesterday's backup has
the potential of causing problems there. There is a procedure for recovering
objects from a corrupt or suspect mdb.
1. Open the bad MDB
2. Open each Form that has a module in design mode
2.a Copy the code in the module and paste it into a text file
2.b Change the form's Has Module property to No
2.c Save the form
3. Do all of number 2 above for all your reports.
4. Create a new MDB
5. Import all the objects from the bad MDB
6. Open each form and report that had a module in design mode
7. Paste the code from the text file into the form/report module
8. Compile
9. Compact and Repair

Hopefully, that should work.

Now if you suspect that one query, don't import it, recreate it.
There is one other trick you could try. That is to open the suspect query,
select SQL view, copy the SQL. Then, in another MDB, create a new query,
select SQL view, and paste the SQL into it. Save it see if it works.

Good Luck
 
Back
Top