the "VBA-project is damaged" every day

[olle]

Hi everyone.
I am BigOlle from sweden and I have been working with Accees for ten
years
I am now working on an project that started in Access97 and since a
few months is continues in Access2000.

My plan is to use Access2000 as it is supposed that mdb-files in
Access 2000-format can be opened from all Access versions after that
one.
(I hope it is so)


It all seemed to work very well until last week when my mdb-file could
be opened on my computer.
(it was at the time about 60 mb)

It showed that I had the wrong version of the Vbe6.dll file, so I
went on from that day on other Pc's

I went back to a working (as it seemed) copy of the database.
( I must tell that my mdb file is working on a linked mdb-file on the
same library on my computer and since one month ago
the data-mdb-file is passwordprotected.)

Now I make a backup of my mdb-every halft an hour as it regulary
happens that I get the error message:
"VBA-project is damaged"


I have tried:
1/ To convert my project till Access2002 and convert it back to
Access2000.
(It sometimes works but sometimes I even get this same error message
in Access2002:
("VBA-project is damaged")

2/ Decompile the project.

3/ Save form modules as text and import the text-modules to the mdb-
version that is not corrupt.

But all the same I regulary (some days many times a day) I get the
errormessage.
("VBA-project is damaged")


I have noticed that on decompile and converting get the message that
the form
FrmMySeachform_070726_1 can't be loaded. And this is when I am
working in the form frmMySearchform.
(I make backup-copies of the forms that I am working on this way)

I hope that someone can give me an advice how I should go on with my
project


Regards BigOlle

 

[Guest]

First, try deleting the form FrmMySeachform_070726_1
If you have a copy from an old backup that was working copy that in. If
this does not work, create a new mdb and copy each object in your current
project into the new mdb or adp, whichever you are using.

 

[David W. Fenton]

First, try deleting the form FrmMySeachform_070726_1
If you have a copy from an old backup that was working copy that
in. If this does not work, create a new mdb and copy each object
in your current project into the new mdb or adp, whichever you are
using.

I would recommend a full decompile/compact/recompile/compact cycle
*before* you try importing into the new database, as undecompiled
objects can carry their corruption with them when imported into a
new MDB.

 

[Guest]

Had you read the post, you would know he has already done those with no
positive results.

 

[David W. Fenton]

Had you read the post, you would know he has already done those
with no positive results.

I didn't claim it would resolve the problem. I said it needed to be
done before the import.

 

[Guest]

I see your point. Thanks, I should have suggested that.

 

[David W. Fenton]

I see your point. Thanks, I should have suggested that.

I'm sure you would have done it yourself without needing to have it
suggested, but you understand what decompile is for, and why it's
needed.

But most people I encounter in the newsgroups are kinda foggy about
these things (not necessarily the original poster, though).

 

[Guest]

Yes, I do understand Decompile and why it is needed. I also know it should
be used sparingly and with caution.
Sometimes when we answer questions, we make assumptions and don't include
enough detail.

 

[David W. Fenton]

Yes, I do understand Decompile and why it is needed. I also know
it should be used sparingly and with caution.

But when you have corrupted objects, that's precisely the purpose
for which it was created, so in this instance, it's not at all
unwarranted.

I also don't think it's nearly as dangerous as many people make it
out to be. I use it all the time (sometimes because I have to, as a
matter of fact -- just this last week tried a conversion of an A97
MDB to A2K and ran it in A2K and A2K2 and without a
decompile/recompile it gave "Nz not found" errors, with no reference
problems. Decompile and recompile in A2K fixed it for A2K, but not
A2K2. Decompile in A2K2 fixed it for A2K2 but broke it again for
A2K. Dunno what the problem was, because fortunately, I won't have
to convert after all), and I have never lost a line of code from a
decompile.

Sometimes when we answer questions, we make assumptions and don't
include enough detail.

I was trying to add a detail left out in your otherwise good advice,
that's all.

 

[Guest]

I understand your intent, and I appreciate the input.

My wariness regarding the decompile is based on reading and the advise of
others. I was once admonished for suggesting it because of the "dangers", so
I have been careful with it's use. I also have used it frequently with no
problems at all.

I have not done a 97 to 2K2 or 2K3 conversion, but at my previous job, when
the corporate standard was to convert to 2K3, there were 97 and 2K apps
floating around. Corporate's guidlines said a direct 97 to 2K3 may have
problems and recommended a 2 step 97 to 2K then 2K to 2K3 procedure. I had
no problems with any conversions. You may give that a go.