Wouldn't it make more sense to leave the back-end in Access 97 format so
that both sets of front-ends could communicate with it?

The fact that Beeyen's encountering problems suggests to me that the
application in question may not have been split.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Arvin Meyer [MVP]" wrote in message
...
I would convert the Access 97 database to the same version as the newer
one. Then import the data, build a query that shows them both and run a
query that finds duplicates. Alternatively, I suggest that you delete and
records from the imported data tables that have already been imported. If
you have an autonumber, add a temporary field to the existing table for the
ID of the new records, and then do an update to any of the many-side tables
to accommodate the new, changed ID values.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

"Beeyen" wrote in message
...
Good Day Mr. Fenton,

What I mean by synchronizes; is having the database from Access 97
synchronize to a converted Access 2003. Perhaps it is referred to as
something else. You see after the Access 97 database was converted to
Access
2003, there remain quite a few users that continued entering data in
Access
97 database. It will be at least another month or so before the users of
Access 97 will have the Access 2003 installed. Although, the queries are
being run from the Access 2003 database, there is a need for data from
Access
97 to be included. So I was hoping there would be a way to match up the
data from Access 97 to Access 2003.

Any assitance you can provide will be much appreciated.

"David W. Fenton" wrote:

=?Utf-8?B?QmVleWVu?= wrote in
:

I can use the information but is it
possible to syn the two different versions of databases? Access 97
to Access 2003, and if so, how?

What do you mean by "synchronize?"

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/