In Access how can I copy a record and any related records?

I need to set up a function in my database where I can copy a record, but
also all of the records that are associated with it in any related tables (of
which there are 6 tables).

The database is a Contact Management system and we need to do this so that
several consultants can have their own record for one particular client as
they deal with different parts of that cleints business.

"Alan Walker" Alan wrote in message
...
I need to set up a function in my database where I can copy a record, but
also all of the records that are associated with it in any related tables
(of
which there are 6 tables).

The database is a Contact Management system and we need to do this so that
several consultants can have their own record for one particular client as
they deal with different parts of that cleints business.

Hi Alan.

In terms of database design this is a bad idea. In a normalised system
you'd have a table for client details and a consultants table with a
one-to-many relationship between the two (each client can have many
consultants). In fact there may even be a case for a many-to-many (a
consultant could also have many clients). Just my 2p worth :-)

Regards,
Keith.
www.keithwilby.com

Good morning Keith -

Agreed for normal daily usage - but say I wanted to port out existing data
to a new db for just one customer? How would one go about copying the data
as the OP requested?

SusanV


"Keith Wilby" wrote in message
...
"Alan Walker" Alan wrote in message
...
I need to set up a function in my database where I can copy a record, but
also all of the records that are associated with it in any related tables
(of
which there are 6 tables).

The database is a Contact Management system and we need to do this so
that
several consultants can have their own record for one particular client
as
they deal with different parts of that cleints business.

Hi Alan.

In terms of database design this is a bad idea. In a normalised system
you'd have a table for client details and a consultants table with a
one-to-many relationship between the two (each client can have many
consultants). In fact there may even be a case for a many-to-many (a
consultant could also have many clients). Just my 2p worth :-)

Regards,
Keith.
www.keithwilby.com