converting from access 97 to access 2002?

[DANIEL SIMPSON]

Hi , Here is the situation:
My client has a custom built database that opens great in
access 97'.
He wants to install the program(its a database) on a
windows xp home machine, which has access 2002 on it.
When i setup all the necessary info i.e. the paths to the
database (which is located on a windows 98 machine running
access 97) everything looks fine.
When i try to open the database on the xp machine running
access 2002 it says that I can't make any changes to the
database unless i convert it (i guess to the 2002 version?)
THE QUESTION: If i convert the database , which is located
on the windows 98 machine running access 97, in order to
view and edit it on the win xp machine running access 2002,
will i be able to go back onto the win 98 machine and use
it as before as well as use it on the win-xp/access 2002
machine? Does it make some sort of a copy so it wont screw
up the original? THE DATABASE NEEDS TO BE EDITABLE FROM
BOTH MACHINES and have the SAME CURRENT INFORMATION! If
there is a way to do this please help!!!
thank you very much,
--daniel

 

[John Nurick]

Hi Daniel,

Access distinguishes between _making changes to the data_ and _making
changes to the database_. If you open an Access 97 database in Access
2002 without converting it, you will be able to change the data (i.e.
add/edit/delete records) as normal but you won't be able to make any
design changes (e.g. add or edit tables, forms, etc.)

Usually the best way to share a database between two networked machines
is to split it into separate front end and back end MDB files. The data
goes in the back end, and the front end just contains the forms and
queries and so on, with linked tables connected to the data in the back
end. Access 97 has a Database Splitter in Tools|Add-Ins which does it
all for you.

When you split the database, the back end MDB needs to go into a shared
folder where all workstations can access it. Put a separate copy of the
front end MDB on each machine. Use the Linked Table Manager to re-link
the front end to the back end after copying. You can now allow Access
2002 to convert its copy of the front end (this won't affect the shared
back end MDB).