Visual basic for application project in database is corrupt

[Guest]

I'm running Office 2003 on Windows XP. I have a database that does not open,
and gives me a message stating that Microsoft Access has detected corruption
in this file. The message goes on to suggest that I run Compact and Repair
Database from the Tools menu. When I do, I get the error message above. Is
there any way of recovering this database?

 

[Guest]

You could create a new empty database and copy each individual table (1 at a
time) into it. Each time run the compact and repair option to ensure you are
not bringing in somethin strange.

Of course you could link the new DB to the old but I think it may be safer
to use the slower method in this case (1 at a time)

After you have done the table start with the queries then the forms,
modules, charts etc etc.

May take a while but it's the safest method.

 

[Guest]

Thank you for your response. I actually tried both ways, linking and
inporting, but I'm unable to gain access to the corrupted database. The only
thing I have been able to do is access it through MSQuery in Excel, but that
only gets me to the data. What I really need is the queries, forms, and
reports. I can re-create the data fairly easily.

 

[Guest]

Try pressing and holding down the shift key when you open the DB

 

[Guest]

have a look at this site

http://www.granite.ab.ca/access/corruptmdbs.htm

good luck

 

[Guest]

Wayne:

I read about those symptoms in that article you referred, and my database is
showing several of them. Questions are...

How did the database get corrupted in the first place?

Why didn't the database show these symptoms on the computer where it was
created? This problem only became apparent when I tried to deploy a .mde
version of the FE. I go back to the parent computer, and none of these
symptoms occur. Is it really corrupted?

Nicole

 

[Paul Shapiro]

Without the beginning of this thread I'm just guessing, but .mde's will have
a problem if the client computer is missing any of the VBA references that
were set on the parent computer. Can you try the .mdb on the client and see
if that works? If not, it's easier to troubleshoot than with the .mde. Start
by opening the VBA editor, go to the Tools menu and choose References. See
if any of the checked ones are marked 'Missing'.
Paul Shapiro

 

[Guest]

Paul:

There were no checked References that were marked "missing" on the client
computer. Also, although the .mdb worked better than the .mde, the Linked
Table Manager still could not find a certain object, and the above articles
imply that this is still a sign of corruption. In addition, the swtichboard
blanked out after using one of the buttons (more unusual behavior).
Nevertheless, I think you're on to something and wonder if you have any more
suggestions.

Nicole

 

[Paul Shapiro]

If you haven't tried it yet, you could make a new blank .mdb. Import all the
items from the old .mdb. The behavior you're describing doesn't sound like
the kind of corruption I've seen. Generally, a corrupted database triggers
an Access application failure. When importing the old objects into the new
database, you might do all the tables first, then the queries, etc. If it
crashes, you've narrowed down the corrupted object. So if it crashes when
you import the forms, you go back and import half the forms, working your
way down until you identify the corrupted object. Hopefully you have a
backup version of that object.

Access has always been challenging for flaws in video drivers. The symptoms
you describe here sound a little more like video driver problems than Access
corruption. You could update the client computer on Microsoft Update, and
maybe check the video card manufacturer's website for the latest stable
drivers. If the Access .mdb works fine on the parent computer, it doesn't
sound like corruption. It sounds like some difference in the computer
hardware/software. If you have other client computers with different
components, you might try one of those. Or a laptop.
Paul Shapiro

 

[Guest]

Paul:

I just may have to consider these points. It is also interesting that when
loading a previous, more juvenile version of the same database onto several
of my client computers, I had no problem at all. Now that I've added a
switchboard, and VBA programming, control buttons, more combo boxes, I get
these errors and I'm being told by some systems that, "Oh yeah, this database
is in an unrecognized format...", etc, etc.

Just to review, it seems that my following courses of action should be to.

1. update all of these computers to the same version of Access that I
created the database in.
2. Make sure that these computers have the most updated video drivers that
the manufacturer provides.
3. If I get the same evidence of possible corruption (even though the
database still shows none whatsoever on the parent computer), create a new
database, copying one section over at a time to narrow the problem. This may
not work on the parent computer.

Also, I'm getting one consistent error with the computers that would let me
open the database. And that is "The Microsoft Jet database could not find
the object 'MyTable'." And I wonder if this could be concrete evidence of
corruption. Only one of these computer have actually kicked me out of Access.

 

[Paul Shapiro]

I didn't realize the computers have various Access versions. If you have the
choice to get them all on the same version, same service pack (hopefully the
latest) and up-to-date from Microsoft Update or whatever patching choices
you use, that's a very strong first course of action.

A corrupted database would show the same problems on all computers. That's
not what you're seeing. I think you're much more likely seeing issues from
system configuration differences.

 

[Tom Wickerath MDB]

you shoudl try not keeping your data in a crappy office format

use a real database, like SQL Server

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[David W. Fenton]

Also, I'm getting one consistent error with the computers that
would let me open the database. And that is "The Microsoft Jet
database could not find the object 'MyTable'." And I wonder if
this could be concrete evidence of corruption. Only one of these
computer have actually kicked me out of Access.

Have you turned off NAME AUTOCORRECT in the database? If not, you
need to do that, as this sounds like the kind of error it produces.

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

rofl

stop blaming everything but your piece of crap architecture

don't blame the network
don't blame ADO
don't blame the wireless

BLAME MDB, JACKASS

 

[Tom Wickerath]

rofl

stop blaming everything but your piece of crap architecture

don't blame the network
don't blame ADO
don't blame the wireless

BLAME MDB, JACKASS

 

[Guest]

Note taken. However, after closely comparing the FE and BE, I realized that
I neglected to sever the connection to table that I had previously deleted in
the BE. I'm relieved the problem was this simple for this specific error.

I've also used the compact and repair feature on the parent computer (and
parent database) and have since then installed this repaired version onto at
least once client computer successfully.

If I need anymore support, I'll be sure to come right back to this same
thread, even with all of its drama.

Nicole