Access 2003 Corrupting 2002 DB

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sandy Ramsey - 09 Mar 2005 16:37 GMT

I have a split FE/BE Access 2002 databases located on a server. The FE is
being shared (I know this is not correct, but they will not allow it loaded
on the client) by about 7 users. One recently had their Office swithed to
2003, including Access. Now if that person opens the database first, it
corrupts the FE. However, if they are the 2nd person to open the database,
everything is fine.

I am thinking that sharing the FE between the 2 versions is causing the
problem. Any other possiblities? Could it be any of the various security
issues with Access 2003?

Reply to this Message

Ken Snell [MVP] - 09 Mar 2005 16:51 GMT

The problem most likely is the sharing of the front end. When the person who
has ACCESS 2003 opens the front end, the file changes the references to
those used by ACCESS 2003. When he/she closes the file, and then someone who
has ACCESS 2002 opens it, those references are no longer valid and the file
will crash/error.

The reason the person who has 2003 isn't seeing an error is because of
backwards compatibility -- his ACCESS sees the older references and updates.
But 2002 has no knowledge about 2003, so it cannot convert backwards.

This is an excellent example of why each user should have his/her own copy
of the front end file.

Signature

Ken Snell
<MS ACCESS MVP>

>I have a split FE/BE Access 2002 databases located on a server. The FE is
> being shared (I know this is not correct, but they will not allow it
[quoted text clipped - 8 lines]
> problem. Any other possiblities? Could it be any of the various security
> issues with Access 2003?

Reply to this Message