Copying records

[Lowell]

I have searched for a method of copying records.

Is there a way to enter all of a person's info once into a form and then create a macro to copy/save to/save as/duplicate the info into two or three tables?



I can only find the copy command for a whole object, such as a complete form, in the macro options. (I have a hard time wrapping my head around code, sorry!)

I don't suppose there is anyway a bound control can have two sources?

The data I need to enter requires two or three different name titles in two or three different tables, but all the other info of course is the same (e.g. place of birth, DOB, parents, age, etc.).

Lowell

[June7]

Why do you want to copy the same data to several tables? This is contrary to basic relational database principles.

A bound control can have only one source.

[Lowell]

Well, I guess I'm a beginner and have only built two or three small databases and have beat my head against the wall and used a stack of scrap paper a foot thick trying to figure a way out to get all this info into the database only once. I finally came to the conclusion that it would have to be entered twice at least because one person in my records can have two names. I'm dealing with a groups personal records that last a lifetime - birth, baptism, marriage, and death. This has to be able to include name changes thru marriage and yet maintain their original status as a child of their original parent as well as become a new record together with the new spouse and create their own group. Then I need to be able to print off records that group the people by status, family, age, etc. Sound complicated? Probably not to you, but to me it seems like a mess. I don't learn fast and only use access in my spare time, so don't have a lot of time to mess with trying things. Maybe I should get someone to do it for me?

Does this make sense?

Lowell

[June7]

Never built anything like this. Sounds like a family tree kind of app.

Want to allow any number of name changes? Maybe an 'Aliases' table is needed?

Want to allow any number of marriages? Maybe a junction table to document the pairings?

Copying the data could involve use of SQL INSERT action.