Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mass export of tables?

Status
Not open for further replies.
May 4, 2004
15
US
Hi guys,

I have two similar databases. One with good code/bad data and one with bad code/good data (!!! could be worse I guess!)

How can I mass export the tables from one to the other without having to rename each table, please?

Many thanks!

HS
 
The error that exists in the "bad code/good data" database appears to be a function of not just the code, but also forms, reports etc. I was using "bad code" for simplicity's sake to describe the situation. If I went your way, I would have to transfer virtually everything but the data with potentially no net gain in productivity.

It appears that an enthusiastic amatuer has made a number of changes. I want to roll back to an earlier version of my application but keep the newer data.

Thanks.
 
What about creating a new database, then import the code, forms, reports, queries... from the "god code" db, and the tables from the "good data" db - it's quite easy, File | Get External Data | Import.

Another way of exporting/(importing everything but the tables, can be found in thread705-834817 (and a link within), which also allows for keeping text file backups of all objects (but the tables)

Before attempting anything, backup, backup and backup (did I mention backup?;-))

Roy-Vidar
 
As a slight variation on the recommendation by RoyVidar, why not create two (2) new databases, one for the data and one for everything else.

1) Import the "Good" data into the Whatever_Data.mdb;
2) Import everything else into the Whatever.mdb.
3) Finally, _link_ the Whatever.mdb to the
Whatever_Data.mdb tables.

This gives you several advantages:
1) You can more easily create a selective back-up of the
the data or the forms, etc. or both;
2) You can put some data recovery, database admin, and
data integrity scans in the Whatever_Data.mdb without
it cluttering up, so to speak, the other database;
3) if you discover that you've foo-barred the data or
the other database, you can more easily recover.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top