move data to new DB

[Husky]

Break through yesterday showed me a better way to have all the titles, and
stars in 2 separate DB's actually all the fields in my form in separate DB's.

I've spent the past few months transferring my VCR's to DVD. And just finished.

The form has made the DVD db 193 megs. Mostly images maybe, or poor design.

But I'm fixing to redesign the form because I still have some VCR's to go, and
will most likely still use them b4 hard copying to DVD.

I figure I'll have a separate DB for each field in the form.

The thing is, rather than retype all 185 DVD records, is there a way to take
the current DB that has all the fields, and migrate them to separate DB's, then
create the new form to use the separate DB's ?

 

[Guest]

...all the fields in my form in separate DB's.

I figure I'll have a separate DB for each field in the form.

You say in separate databases but your comments sound like separate tables.
Which is it?

Actually you do not need different tables - just put a flag field for the
type. C-CVHS, D- DVD, V-VHS, B-Beta, 8-8mm

The thing is, rather than retype all 185 DVD records, is there a way to take
the current DB that has all the fields, and migrate them to separate DB's, then
create the new form to use the separate DB's ?

There is no need to re-type everything – just use append queries.

 

[fredg]

Break through yesterday showed me a better way to have all the titles, and
stars in 2 separate DB's actually all the fields in my form in separate DB's.

I've spent the past few months transferring my VCR's to DVD. And just finished.

The form has made the DVD db 193 megs. Mostly images maybe, or poor design.

But I'm fixing to redesign the form because I still have some VCR's to go, and
will most likely still use them b4 hard copying to DVD.

I figure I'll have a separate DB for each field in the form.

The thing is, rather than retype all 185 DVD records, is there a way to take
the current DB that has all the fields, and migrate them to separate DB's, then
create the new form to use the separate DB's ?

Open the new database.
Click on File + Get External data + Import
Navigate to the old database.
Click on tables.
Select the tables you wish to import
Click on Options
Place a check mark in the Import Relationships box.
Select the Table Definition and Data
Then select any other object in the old database you also want.
Click OK

 

[Husky]

On Thu, 20 Oct 2005 12:20:06 -0700, "KARL DEWEY"

Ok the DB is called DVD, there's one videos table that includes all the other
tables.
1 2 3 4
tower, titles, names, colors,
1 which tower they're stored in.
2 titles on the DVD
3 about 15 names of stars on each DVD.
4 color of DVD case.

You say in separate databases but your comments sound like separate tables.
Which is it?

Actually you do not need different tables - just put a flag field for the
type. C-CVHS, D- DVD, V-VHS, B-Beta, 8-8mm

It's strictly a DVD DB. I also have a vhs db. reason being the DVD holds more
titles than the vhs. Also when I printout the VHS labels, the DVD db/table
won't cut it cause of number of titles on 1 DVD. A vhs holds about a max of 4
titles.

There is no need to re-type everything – just use append queries.

I don't really know what append queries is, but I'll look.

 

[Husky]

Open the new database.
Click on File + Get External data + Import
Navigate to the old database.
Click on tables.
Select the tables you wish to import
Click on Options
Place a check mark in the Import Relationships box.
Select the Table Definition and Data
Then select any other object in the old database you also want.
Click OK

Never even thought of that. All my tables are imported to start with.