I need help to transfer data.

I have been redesigning My Access200 database business software.

The redesign is done on a copy a few months old and now I want to dump all
the data from the current one into the redesigned one.

My first idea is to use the import wizard to transfer the current tables and
other objects over into the redesigned system, but I am concerned about the
integrity of all the reationships with this method.

e.g. If I import a table "tblCustOrders" of the new data, this is installed
as "tblCustOrders1" in the redesigned database, and if I attemp to change
this latter's name to "tblCustOrders" I am asked if I want to replace the
old table - which then involves breaking a relationship. Should I go ahead
anyway?

Can someone give me a start on how to effectively transport the new data
over?

Regards, Frank

Frank

Rather than copy the tables, structure/data and all, how 'bout simply
importing the data into the redesigned structure?

If you open the re-design, link to the former .mdb, and create append
queries, you can suck the data out of the old tables and stick it into the
new ones.

--
Good luck

Jeff Boyce
Access MVP

"Frank Martin" wrote in message
...
I have been redesigning My Access200 database business software.

The redesign is done on a copy a few months old and now I want to dump all
the data from the current one into the redesigned one.

My first idea is to use the import wizard to transfer the current tables
and
other objects over into the redesigned system, but I am concerned about
the
integrity of all the reationships with this method.

e.g. If I import a table "tblCustOrders" of the new data, this is
installed
as "tblCustOrders1" in the redesigned database, and if I attemp to change
this latter's name to "tblCustOrders" I am asked if I want to replace the
old table - which then involves breaking a relationship. Should I go
ahead
anyway?

Can someone give me a start on how to effectively transport the new data
over?

Regards, Frank

Thanks. It's hard to transfer the data across because the whole
customer/addresses system has changed including IDs. Anyway I am
transferring the tables accross and then renaming these to the the names of
the incumbents'.

Then I have to fix all the relationships in the relationship window which
means also that I have to fix up the integrity sometimes, which means going
over the tables and entering missing fields/IDs.

All my data goes back to 1999 so I have to be careful.
I have already used the update queries to insert the new AddressIDs next
(another column) to the old ones.

So far all has gone well, though I will be adding data to the old and new
databases separately for a while - just in case.






"Jeff Boyce" -DISCARD_HYPHEN_TO_END wrote in message
...
Frank

Rather than copy the tables, structure/data and all, how 'bout simply
importing the data into the redesigned structure?

If you open the re-design, link to the former .mdb, and create append
queries, you can suck the data out of the old tables and stick it into the
new ones.

--
Good luck

Jeff Boyce
Access MVP

"Frank Martin" wrote in message
...
I have been redesigning My Access200 database business software.

The redesign is done on a copy a few months old and now I want to dump
all
the data from the current one into the redesigned one.

My first idea is to use the import wizard to transfer the current tables
and
other objects over into the redesigned system, but I am concerned about
the
integrity of all the reationships with this method.

e.g. If I import a table "tblCustOrders" of the new data, this is
installed
as "tblCustOrders1" in the redesigned database, and if I attemp to
change
this latter's name to "tblCustOrders" I am asked if I want to replace
the
old table - which then involves breaking a relationship. Should I go
ahead
anyway?

Can someone give me a start on how to effectively transport the new data
over?

Regards, Frank