Compatability issues Access 2002 and 2003 (Win XP Access 2003)

Topic

New Reply

I have a DB written in Access 2003, format 2000. I copy this to another computer running Access 2002. Everything seems to function OK, except for the Switchboard. Changes made under Access 2003 are not reflected under 2002!

Both are using Windows 5.1, SP-2.

What problems can I have with running the Access 2003 program under Access 2002?

Reply | Quote

Replies

What exactly do you mean by “Changes made under Access 2003 are not reflected under 2002!”?

Reply | Quote

If I modify the SwitchBoard in Access 2003, the modifications are not reflected in the Access 2002 copy. I manually changed the copy in the 2002 copy, and everything functions. Should I get problems when changing from Access 2003 to Access 2002 as long as the file format is 2000, or is this something I am doing wrong? (That is the normal reason for my problems.)

See you Monday.

Reply | Quote

I suspect that there was a mix-up, i.e. either the original database was still used in Access 2002, or the wrong form was modified. What you describe is impossible.

Reply | Quote

Anything is possible, and an error on my part is probable. The back-end data base also lost a table. It suddenly filled with “error” indications. All this happened at the same time. Fortunately, I had a back-up, and could fix the lost table. Anyway……

Thanks for the help.

Reply | Quote

I think there may be a conceptual issue here. The concensus on Access database implementation says to split the database into a front-end and a back-end and then give each user their own copy of the front-end. When you do that, making design changes involves giving each user a new copy each time a set of changes is deployed. (From 2000 forward, you can only make changes to forms, reports and code if you have exclusive access to the database.) So that would explain why you didn’t see design changes on the 2002 system after making them in the 2003 system. The corruption of the back-end is likely unrelated – most probably the result of either a LAN problem, or a workstation or Access crash.

Reply | Quote