Upgraded to ACCESS 2007 - VBA PROJECT error

[Steve.]

I was using Access 2003 and upgraded to ACCESS2007 but my old app will not
wok. I get the following msg:
The database cannot be opened because the VBA project contained in it cannot
be read. The database can be opened only if the

VBA project is first deleted. Deleting the VBA project removes all code
from modules, forms and reports. You should back up

Your database before attempting to open the database and delete the VBA
project.


I am unable to do anything and have to use task mgr to cancel ACCESS. My
database is then corrupted and can not be used by ACCESS 2003 or ACCESS2007.
ANy ideas how to correct this prob?

 

[Maurice]

Steve,

Can you start the app by holding shift? Try the following options:

1. open the 2003 version (holding shift)
2. if possible go to the VBA window and check to see if no references are
missing
3. if possible try to compile the code via the debug menu option
4. If all went well try converting that version to 2007

Try the same with the 2007 options.

Another option could be
Create an empty fresh db
Import the various objects piece by piece (keep compiling in between)
Compact and repair...

Finally; try running under administrator rights (i assume you ar doing this
but just in case).

maybe any pointers in here that could be a solution...

 

[Steve.]

I could do this but the problem is that ACCESS 2007 is slowly being installed
to the PC's across my department. It may be the endo of the yr before all
users are upgraded.

 

[Maurice]

I get it but what I meant to say was try this with one version of your db and
if you can get it to work go on with that version for distribution.

 

[Steve.]

I only have one version of the database located on a shared drive. We do no
distribute the app to the users. They all use the same App and db by going to
the shared drive. ACCESS 2007 is being pushed out to the individual pc's,
not the app.

 

[Douglas J. Steele]

That's a mistake.

The application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables and relations). Only the back-end should be on the server. Each user
should have his/her own copy of the front-end, ideally on his/her hard
drive.

 

[Tony Toews [MVP]]

I only have one version of the database located on a shared drive. We do no
distribute the app to the users. They all use the same App and db by going to
the shared drive. ACCESS 2007 is being pushed out to the individual pc's,
not the app.

Indeed using a shared database may have caused your problems in the
first place.

You want to split the MDB into a Front End MDB containing the queries,
forms, reports, macros and modules with just the tables and
relationships in the Back End MDB. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite
nicely.

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's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Steve.]

Thanks, but this will now become a Maintenance pain. Now we will have to
keep track of all users and make it a major project just to keep all the
sofware in sync. You would think MS would design products that are backward
compatible so that migration to newer versions would be transparent. If Link
table design is the prefered method, then that would be the only option.

 

[Douglas J. Steele]

If you use Tony's Auto FE Updater (the link to
http://www.granite.ab.ca/access/autofe.htm he posted earlier), you don't
have to do anything to ensure that the users have the most up-to-date copy
of the front-end.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

 

[Tony Toews [MVP]]

Thanks, but this will now become a Maintenance pain. Now we will have to
keep track of all users and make it a major project just to keep all the
sofware in sync.

Like Doug said either my Auto FE Updater or other solution, links
found on that page, make this maintenance pain a non pain.

You would think MS would design products that are backward
compatible so that migration to newer versions would be transparent. If Link
table design is the prefered method, then that would be the only option.

I don't quite understand your comment about backwards compatible as
this has been the recommended practice since at least Access 2.0.
Could you also expand on your Linktable design question as I don't
understand that either?

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's Microsoft Access Blog - http://msmvps.com/blogs/access/