Copying Multi-Tabbed Record

Kavarria

New member
Local time
Today, 15:13
Joined
Jun 7, 2010
Messages
8
I have a form/record with multiple tabs and I want to copy it into another form keeping it exactly the same, with all the tabs the way they are and all the information intact. I've been able to copy the first tab, but I can't get any of the other tabs to copy.
 
Welcome to AWF!

Could you explain what you mean by copy a tab?
 
I have a record which has tabs. And I was to copy the whole record into another one. The problem I'm coming across is, I'm only getting it to copy the first tab such that the new record only has one tab with the information on the first tab of the old record. I want the new record to be exactly the same as the other record, tabs included.

I hope that clarified.
 
First of all, this sounds like a very BAD design. You should not be trying to copy entire records like this. What is the purpose?

Second, are the tabs part of the same record or are they using subforms to be able to use additional tables?
 
I'm guessing what you want to do is synch your tabs with an ID of some sort?
 
I'm guessing what you want to do is synch your tabs with an ID of some sort?

Yes, the tabs/subforms are all linked with an ID#. I want to increment/change the ID# on the new set of tabs/subforms and then copy all the remaining information.
 
then copy all the remaining information.
That means that your design is flawed. You should not be storing redundant data. Copying the same field information over and over again is a normalization problem. What type of data are you trying to store over and over again?
 
Basically, you want to copy it such that the new record is "auto-filled" with the previous/copied record?

Edit: Oops late post.
 
That means that your design is flawed.

Don't tell me the design is flawed. I don't want to be told about how the design is flawed. That's not my job. My job is to make it work. So either help or be quiet.

What type of data are you trying to store over and over again?

It's version data. It's exactly the same except for the version number.
 
Basically, you want to copy it such that the new record is "auto-filled" with the previous/copied record?

Yes! :) That's right. Just I want the ID# to be different from the previous record.
 
Don't tell me the design is flawed. I don't want to be told about how the design is flawed. That's not my job. My job is to make it work. So either help or be quiet.
Wrong move Kavarria. You may notice that Bob has been on this forum for a very long time, almost during the site's inception. He does bring a vast amount of experience here too and all in done in good will (without gain). Maybe you haven't explained your problem properly and he has based his response on what he's been told so far.

All he's doing is trying to help!
 
Don't tell me the design is flawed. I don't want to be told about how the design is flawed. That's not my job. My job is to make it work. So either help or be quiet.
We don't just give answers to do band-aid fixes on this forum. We try to educate and to get the RIGHT answers. And, if you continue on the path you are taking, you might be able to get it to work, but at what cost? Your data redundancy will

1. Take up more space than necessary.
2. Create potential reporting problems in the future.
3. make life a living hell for those who follow you.

Unless you have absolutely no control whatsoever over the tables that you have (there are those situations, as I am well aware), you should FIX your design issues and not be so quick to blow off my answers.

And so with that I will bow out of this thread and I will not attempt to help you anymore as it is clear you can not handle the truth. If someone wishes to give you the band-aid fixes, that is their perogative.


It's version data. It's exactly the same except for the version number.
Then you do NOT need to store the same data over and over and you should instead have a junction table for a one-to-many situation.

Normalize.png


headinhands.jpg
 
I do not have any control over the tables. Though I could probably get it if I had a good solution.
 
Hmm... I thought I saw a different response to this?

If all you want to have is a sort of copy and paste function, which would be useful for repetitive data entry, then use the Tag property of the control and for pasting iterate through the controls and paste into it. Enable the PASTE button ONLY for new records and disable it after the paste. Empty the control's tag as well.

If you're going to copy and paste all the fields, then that's not the solution for you.
 
if you continue on the path you are taking, you might be able to get it to work, but at what cost? Your data redundancy will
1. Take up more space than necessary.
2. Create potential reporting problems in the future.
3. make life a living hell for those who follow you.
...
Then you do NOT need to store the same data over and over and you should instead have a junction table for a one-to-many situation.

Yes, you are right. I am sorry, I over-reacted. It just seemed you were picking me apart rather than helping.

I like the idea of the junction table. I'm not sure how to implement it though. I'd have a bunch of ID#'s needing to be linked to the same information..I have a feeling there's a query somewhere in here.
 

Users who are viewing this thread

Back
Top Bottom