copy data from a column in one table to a column another.

[Nats]

Please would you be able to advise me how I would copy data from a column in one table to a column another table.

But I need to only use table not a query.

Thank you in advance for your help.

 

[neileg]

You have to do something to copy the data. You could use a query, or VBA or you could do a copy and paste in table view.

Perhaps you could explain why and in what circumstances you want to copy the data.

 

[qurn]

I have the same question, I'd like mine to copy from an auto number column after update, and I'd like to do it in VBA. Could I get the code for that please?

 

[neileg]

I have the same question, I'd like mine to copy from an auto number column after update, and I'd like to do it in VBA. Could I get the code for that please?

Just so any advice is in context, why do you want to do this? Duplicating data is usually frowned on.

 

[qurn]

Well, I need it to complete relationships for updates. I'm trying to get it so my users can update from one form.

I don't know how else to put it. The info is spread acrost a couple of tables then put together in a query (fairly common). Even with the relationships it's not automaticaly filling in the ID numbers.

 

[neileg]

You would normally handle this in a form/subform setup. Providing the parent/child links are correctly set (perhaps using the subform wizard) then Access will automatically populate the child table with the ID.

 

[qurn]

Ok, I tried that it never seems to work for me. Do I need reinforce referencial integrity in order for it to work?

 

[qurn]

any help from anybody?

 

[The_Doc_Man]

referencial integrity in order for it to work

No. There has to be a defined relationship first, but RI is not required for this particular feature.

Build the parent table. Build the child table. Define the relationship.

NOW build the form for the parent. Build another (smaller) form for the child. Add a sub-form control to the parent with the sub-form wizard enabled.

The wizard will ask you to identify the form that goes into the sub-form. If there is a pre-defined relationship, it will ask you to confirm that the parent & child relationship are the two fields involved in the defined relationship. If so, you are done. (If not, it will ask you to name the parent link and child link field names.)

Thereafter, if you bring up the parent and at least one child exists, you will bring up the child form too. You will have separate navigation tools on the bottom of the sub-form control as well as at the bottom of the parent form.

They are not quite independent. If you change from one child to another, the parent stays put. If you change from one parent to another, the child should change.

 

[qurn]

Ok, sweet, thanks. I see know that you need to use a subform. I was using one single form based on a query, so there's the indiscrepancy. I'm assuming I can make it look like only one form without it looking like a form with a bunch of subforms on it?

I'll try this out, but just for curiosities sake could some one teach me the VBA code so I can try both out and see which one I like?

 

[neileg]

??

If you have a one to many relationship between parent and child then you need a subform to deal with multiple child records.

If you have a one to one relationship, you probably should hold all the data in one table.