Access 2007 or Vista corrupts mdb?

  • Thread starter Thread starter ericgj
  • Start date Start date
E

ericgj

We have an Access 2002/2003 format mdb shared by a number of users on a local
network. A new user wants to use Access 2007 rather than 2003 to open it,
however every time he does, it corrupts the file badly ("microsoft jet
database engine could not find the object msysdb"). Jetcomp.exe cannot save
it.

Have you heard of this happening and what is the workaround? It seems to be
the same problem mentioned here, which the author attributes to Vista rather
than Access 2007 per se:
http://www.tech-archive.net/Archive/Access/microsoft.public.access.setupconfig/2008-12/msg00003.html

Thanks for any advice.
Eric
 
Well, that would be the problem. You have Access 2003 users and Access 2007
users trying to open the same the database. You will need to split the
database and give each user their own front end. In addition the Access
2007 user will need to add their front-end to the databse to 'Trusted
Locations' under Security.
 
Thanks for your help.
Could I have two front ends then, one for Access 2003 users and one for
Access 2007 users? Instead of one front end per user - a nightmare to manage?

BTW, no where did I find this documented. Everywhere it says 'no problem
using 2007 to open 2003'. So I assumed like between 2000 and 2003 you could
have users on either version at the same time.
 
Thanks for your help.
Could I have two front ends then, one for Access 2003 users and one for
Access 2007 users? Instead of one front end per user - a nightmare to
manage?
Click to expand...

It's not a nightmare to manage. There are utilities to automatically
push updated front ends to users (Tony Toew's free one for example).
With a fast LAN and a smallish file you can even just copy the front end
to their PC every time they open the application by having them use a
shortcut that points to a batch file or script.
BTW, no where did I find this documented. Everywhere it says 'no
problem using 2007 to open 2003'. So I assumed like between 2000 and
2003 you could have users on either version at the same time.
Click to expand...

It's the "at the same time" part that is not a good idea. Actually it's
not a good idea even when everyone is using the same version, but it's
*really* a bad idea when the versions are mixed.
 
Back
Top