Transferring Data to Newly Designed DB

[S Jackson]

I have redesigned my database and now I want to copy and paste records into
the appropriate tables. However, when I attempt to do this in I get a
message about having to have a related record in another table
(relationships).

To get around this, do I have to temporaily delete the relationships and
then paste in the records? Or is there a better way to do this?

TIA
S. Jackson

 

[Immanuel Sibero]

Hi

You may have to resort to 'temporarily delete the relationships', but you
should load your independent (primary tables) first. For example, if you
have Customer and CustomerOrder tables, you would load the Customer table
first.

HTH
Immanuel Sibero

 

[Albert D. Kallal]

I would think the better approach is to leave the tables alone, and import
your code and forms.

For the future, read up on how we split our databases, and thus we keep the
code/forms separate from the data.

Check out:
http://www.granite.ab.ca/access/splitapp.htm

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm

 

[PC Datasheet]

Temporaily deleting the relationships and then pasting in the records will fail
when you try and recreate the relationships! You'll get the same message as you
are getting now!

 

[John Vinson]

I have redesigned my database and now I want to copy and paste records into
the appropriate tables. However, when I attempt to do this in I get a
message about having to have a related record in another table
(relationships).

To get around this, do I have to temporaily delete the relationships and
then paste in the records? Or is there a better way to do this?

An Append query would almost surely be a better way! Append "top down"
- append first to the "one" side tables (all your 'lookup tables' in
particular); then the "one-est" of the tables, the "master table" if
you have one, so that the related tables have values to which to link.
Then append to the tables linked to this table, and so on.

If the redesign has changed the relationships, you need to be sure
that the data in the tables in fact meets the relational integrity
constraints that you have set up.

 

[S. Jackson]

Thanks Albert, but my original database was poorly designed and it required
that I recreate some of the tables.

S. Jackson

 

[Albert D. Kallal]

As John in this thread mentioned, you can use append queries, and the
autonumber ID are NOT changed.

Generally, append queries are much better then cut and past, and other
dangerous solutions. So, use the query builder to make some append queries.

So, just make sure you import the topmost tables first, and then work your
way down to the child tables.