Database breakdown

[Guest]

I'm not sure where to get post this. Some of the problems seem to be form
related, others are report problems.

I've been getting error messages on a database that has worked pretty well
for a couple of months. Most of the errors say Invalid Procedure call or
argument. These seeming come out of nowhere on insignificant actions like
selecting from a combo box. When I use the form to open a report I get "The
Open Report action was cancelled." I looked at a report that had an On Open
event. I get the same message as on the form "Invalid Procedure call or
argument". I stripped all the code out of the report and got it to run, but
that is not a solution.

Essentially none of my code is working with a few small exceptions. I have
tried the compact and repair several times already. I want to salvage as
much as I can from this database without importing whatever corrupted element
might be causing this to happen.

I'm open to suggestion.

TIA
Paul Hammond
Richmond, VA
--

 

[John Vinson]

Essentially none of my code is working with a few small exceptions. I have
tried the compact and repair several times already. I want to salvage as
much as I can from this database without importing whatever corrupted element
might be causing this to happen.

Check out the suggestions at

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

Decompiling may be one solution; importing objects one at a time may
be necessary.

John W. Vinson[MVP]

 

[Guest]

Thanks, I've bookmarked the site.

Before you posted I tried importing all the objects, save one that concerned
me, into a new database. I still received some odd error messages till I
compacted and repaired the new database. So far peace has been restored.
I'm keeping my fingers crossed. It's very disturbing to think so much work
could become useless junk. I'm going to have to study up on database repair
and recovery.

Paul

 

[John Vinson]

Thanks, I've bookmarked the site.

Before you posted I tried importing all the objects, save one that concerned
me, into a new database. I still received some odd error messages till I
compacted and repaired the new database.

An essential step, yes.

So far peace has been restored.
Good!

I'm keeping my fingers crossed. It's very disturbing to think so much work
could become useless junk. I'm going to have to study up on database repair
and recovery.

Not to mention keeping CURRENT secure backups. The only database that
doesn't need to be backed up is one that you don't mind recreating
from scratch (at the most inconvenient possible time of course).

John W. Vinson[MVP]