Opening 97 format database in 2003 - help!

[Martin]

Hi - we've got a couple of big databases in Access 97 and need to keep them
in that format until everyone's been upgraded to 2003. We're going to go
with opening rather than converting so that users still in 97 can carry on
working.

The problem is that 2003 users are not allowed to change the design of the
databases in any way. Does anyone know (or know of a link) a list of VBA
keywords I should word-search on to see if this if feasible? I guess any
make table queries being run with DoCmd.Open are a start but then there's all
the DAO/ADO ways of changing the design - all things that won't run if a 2003
user tries to run that particular macro.

Thanks

 

[Keith Wilby]

Hi - we've got a couple of big databases in Access 97 and need to keep
them
in that format until everyone's been upgraded to 2003. We're going to go
with opening rather than converting so that users still in 97 can carry on
working.

The problem is that 2003 users are not allowed to change the design of the
databases in any way. Does anyone know (or know of a link) a list of VBA
keywords I should word-search on to see if this if feasible? I guess any
make table queries being run with DoCmd.Open are a start but then there's
all
the DAO/ADO ways of changing the design - all things that won't run if a
2003
user tries to run that particular macro.

Thanks

If your app is split then keep the BE in A97 and link to it using the
version appropriate to each user. I've never tried it but I think linking
to a 97 BE from a 2k3 FE ought to work.

Keith.
www.keithwilby.com

 

[Martin]

Thanks Keith - in an ideal world you're right. Unfortunately (for various
historical reasons and the way people work here) these databases have to stay
self-contained. They also have a vast amount of VBA which is why I'm keen to
track down and fix any of the routines that make illegal design changes.

 

[Martin]

I'm finding that if VBA makes changes - e.g. uses DROP TABLE to delete a
query and then creates another by way of DAO - there isn't a problem. Is
this right? I thought any design changes couldn't be made by version 2003 to
a 97-format database.

 

[Klatuu]

Now you are experiencing the tribulations of inadequate database design.
There is never any valid reason a database has to be self contained other
than poor design. You should always have a front end and a back end. Back
ends are for data only. A copy of the front end should be on each user's
computer. Sorry, but I had to do a little preaching. I know you can't do
anything about it at this point, but moving forward, find a way to split the
database and do it properly,

You are stuck in a very bad situation. The differences between 97 and 2003
are significant and you may not be able to get around all the problems. One
thing of note that I read in research for upgrading is that it is recommended
that you not convert directly from 97 to 2003. It would be much smoother to
first convert to 2000, then convert to 2003.