"advance scout" <(E-Mail Removed)> wrote:
>the exact error is " Compile error: automation error"
>
>So the question is why would I get this error after the database has been
>repaired? Since the data is all there once this is fixed I will have a
>working database. I have tried compiling... to no avail.
Interestingly enough a client had a very similar problem with an MDB
he was working in. Fortunately it was the front end and fortunately I
had made a copy at 10 am that morning and it only took a few minutes
to put my updates in it.
What is particularly interesting is that we could compact and repair
the front end just fine. However we were still getting the message
"has detected corruption in the file. To try to repair the corruption
...." I also couldn't get into any code. I could get into form design
view.
So clearly the VBA was somehow corrupted.
From your other postings it sounds like you should be fine as you
stated you can get access to the tables. And you have a two month old
copy of the other objects which is up to date.
One thing you could try is decompiling.
Decompile or how to reduce Microsoft Access MDB/MDE size and decrease
start-up times
http://www.granite.ab.ca/access/decompile.htm
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm