Need Direction - Map one access mdb to another

A

AK

Hello All,

I am really all turned around. New enough to not know better!!!!

Problem Setup:

I have made some changes to my VB application so it captures more data and
writes it th a database. In the writing of my Version 2 of my app, I took
my existing db and just added the necessary additional tables, and added a
few fields to some of the pre-existing tables, and created new relations for
those the new tables back to the old tables. (may have changes some of the
relations between the old tables too. But just in a few places.

Some of my records are autonumbered.

Problem Statement:
I want to get the old data into the new database, yet find that it is not as
simple as a cut and paste or an import. I thought for example that on those
tables that have had no change in structure, that I could just copy the info
out of the earlier database and plop it into the corresponding new database
table. Problem is with the auto numbering. The new db renumbers them, and
of course this screws up the relations the records in one table are supposed
to have with other tables.


Here is what I propose doing to map my database. Is this the way it is done,
or is there an easier way? Or will this crater too???


Open up the relations view of my new database.

Do a file import of all the tables and data from the old database into the
new database. (Thank goodness Access will auto remane tables which would
have duplicate names otherwise).

I then propose to arrange the imported tables to match the layout of the
ealrier tables.

I would then add new tables as needed to match so that at the end of the
"mirroring" my tables would be the same.

I propose to then mirror the links on the imported/added tables, then delet
all the old tables, the rename the the new tables to their old name was.
(Table ProjectNumbers1 becomes ProjectNumbers (the name of the corresponding
table in the old database.)

I propose that this will create a mapping by proxy of the old data to the
new database structure.
 
G

Guest

Hello AK,

To be honest, I do not understand your mapping strategy. Nonetheless, you
can create linked tables to your existing data (or import the tables, your
choice), and then run append queries to append (add) the data from the source
tables to the new target tables. JET will allow you to append an existing
autonumber PK, as long as that value has not already been used.

If you already have relations with referential integrity defined, you'll
need to append records to parent (one side) tables first, before appending
records to child (many side) tables. Are you familiar with creating append
queries?


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top