Oren

First, if you did an exact copy, you'd expect that "Field_1" of "Table_2"
would match "Field_1" of "Table_1" (?perhaps the "Field_2" was a type?).

Next, relationships are independent objects. Just because Table_1 was
related to some other table, does not mean a copy of it will be, until you
establish that relationship.

Third, if T_2 is a copy of T_1, then all the fields in both would be
identical.

Finally, what's your underlying business need for having an identical copy?
It's fairly rare that you need to duplicate table structure in a
well-design, well-normalized database.

Good luck!

Jeff Boyce
<Access MVP>

I copy tables to preserve copies of data dumps from the AS400 in the central
office that I have sorted into specific categories, identified and deleted
bad records, and mapped to our engineering database. Each copy receives a
name based on the current date. Each of these data imports overwrites
existing data when it is finally posted to the system, and we need to
preserve values monthly to facilitate planning and forecasting of future
needs. I work for a public utility. How would I preserve these discrete
sets of data that took so much work to build if I don't copy the tables?


"Jeff Boyce" <JeffBoyce_IF (AT) msn (DOT) com> wrote

I forgot to mention that each data import ends up containing over 500,000
records AFTER it is cleaned up. I have received as many as 1,550,000
records in the initial dump. The AS400 ppl give me just 3 days to get it
off the server before they delete it FOREVER. They either cannot or will
not provide historical information.


"junkmail1" <junkmail1 (AT) triad (DOT) rr.com> wrote