VB for Applications project in the Database is Corrupt

  • Thread starter Thread starter Ed
  • Start date Start date
E

Ed

I wrote a dB that has VB code in it. I originally wrote
and compiled the dB with Access 2002. I just upgraded to
Access 2003. I needed to make some changes to the dB and
re-compile it. When I published it for the users, anyone
who upgrade to 2003 had no problems using it. Any users
who are still on 2002 get the following error: "The
Visual Basic for Applications project in the Database is
corrupt."

Having all the users upgrade to 2003 is not possible at
the present time. Any ideas why this is happening? Or
do I need to down grade back to 2002?

Thanks
 
As a general rule, Access databases written in a later format cannot be read
by PCs having only an earlier version installed.
So while your A2003 users can read A2002 database format, your A2002 users
can't read A2003 format.

HTH
- Turtle
 
Ed said:
I wrote a dB that has VB code in it. I originally wrote
and compiled the dB with Access 2002. I just upgraded to
Access 2003. I needed to make some changes to the dB and
re-compile it. When I published it for the users, anyone
who upgrade to 2003 had no problems using it. Any users
who are still on 2002 get the following error: "The
Visual Basic for Applications project in the Database is
corrupt."
Click to expand...

This is a misleading message. A2002 users can't run an A2003
formatted MDE. I'm assuming your distributing an MDE.
Having all the users upgrade to 2003 is not possible at
the present time. Any ideas why this is happening? Or
do I need to down grade back to 2002?
Click to expand...

Yes, you need to ensure that you are working in an A2002 format MDB.
And you must make the MDE using A2002 and not A2003.

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
 
Thanks for the suggestions. I looked in A2003 and under Tools - Database Utilities - Convert Database, the choice is To Access 2002-2003, which leads me to believe the format for A2002 and A2003 is one in the same. Any other suggestions?

Thanks

----- Tony Toews wrote: -----

Ed said:
I wrote a dB that has VB code in it. I originally wrote
and compiled the dB with Access 2002. I just upgraded to
Access 2003. I needed to make some changes to the dB and
re-compile it. When I published it for the users, anyone
who upgrade to 2003 had no problems using it. Any users
who are still on 2002 get the following error: "The
Visual Basic for Applications project in the Database is
corrupt."
Click to expand...

This is a misleading message. A2002 users can't run an A2003
formatted MDE. I'm assuming your distributing an MDE.
Having all the users upgrade to 2003 is not possible at
the present time. Any ideas why this is happening? Or
do I need to down grade back to 2002?
Click to expand...

Yes, you need to ensure that you are working in an A2002 format MDB.
And you must make the MDE using A2002 and not A2003.

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
 
ED said:
Thanks for the suggestions. I looked in A2003 and under Tools - Database Utilities - Convert Database, the choice is To Access 2002-2003, which leads me to believe the format for A2002 and A2003 is one in the same. Any other suggestions?
Click to expand...

Are you distributing an MDE or MDB?

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
 
A MDE

----- Tony Toews wrote: -----

ED said:
Thanks for the suggestions. I looked in A2003 and under Tools - Database Utilities - Convert Database, the choice is To Access 2002-2003, which leads me to believe the format for A2002 and A2003 is one in the same. Any other suggestions?
Click to expand...

Are you distributing an MDE or MDB?

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
 
Ed said:
A MDE
Click to expand...

So you're creating the MDE using A2003. Which means that even though
it is in A2002 format the compiled VB code is in A2003 format. Which
is why the A2002 users are getting this message. And the A2003 users
are just fine.

The next patch out for A2002 will change this misleading message to
one more indicative of the problem.

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
 
Tony,

Thanks for the help. I removed the A2003 from my Office 2003 installation and reinstalled A2002. I was then able to re-publish without any problems.

----- Tony Toews wrote: -----

Ed said:
A MDE
Click to expand...

So you're creating the MDE using A2003. Which means that even though
it is in A2002 format the compiled VB code is in A2003 format. Which
is why the A2002 users are getting this message. And the A2003 users
are just fine.

The next patch out for A2002 will change this misleading message to
one more indicative of the problem.

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
 
Ed said:
Thanks for the help. I removed the A2003 from my Office 2003 installation and reinstalled A2002. I was then able to re-publish without any problems.
Click to expand...

Glad to hear that worked.

BTW you can have multiple versions of Access on your system with a few
caveats.

You need to add explicit path and file names of the appropriate
versions of access to all the shortcuts. For example "C:\Program
Files\Microsoft Office 97\Office\msaccess.exe". Including the quotes
if you have any spaces in the path name which is very likely.

There are some programs out there which will automatically start the
appropriate version of Access.

One of those is ACCVER - Allows you to work with multiple versions of
MS Access databases. Detects the version of Access used to create your
MDB, MDE or MDA files and either reports the version number or starts
the appropriate version of MS Access. www.aylott.com.au/software.htm

Also see: INFO: Access 2000/Access 97 Coexistence FEPs (Frequently
Experienced Problems)
http://www.trigeminal.com/usenet/usenet019.asp?1033

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
 
Back
Top