Re: Creating duplicate rows of data based on a determined number o
- From: "Jeff Boyce" <nonsense@xxxxxxxxxxxx>
- Date: Wed, 10 Jan 2007 14:03:34 -0800
Anne
It is unusual to create "dummy" records, to be filled (or ?unique-itized?)
at some later point. The part of what you originally asked about that still
concerns me is the need for "identical" records. If these records are
destined to end up unique, why do you need "identical" records to begin
with?
Is there a reason you couldn't create a new item's record only when there
was sufficient information to satisfy your "uniqueness" constraint?
Are you saying that there are SOME elements that will be the same across all
of the related (?5) items? If so, you may benefit from revisiting your data
structure. If a group of items have common elements, those, represent a
"parent" quality over the entire set, to be stored in a related table, not
the same table as the "children".
Have I confused you enough yet?<g>
Regards
Jeff Boyce
Microsoft Office/Access MVP
"Anne" <Anne@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:25FDCA26-696E-49E8-900F-177C4413E729@xxxxxxxxxxxxxxxx
Yes- we're using Access. It is for creating production records that will
become unique during the production process. In the beginning we will
have
only 5 items of information. The user needs to be able to create a
specified
number of this record that will be uniquely identified only by their auto
number id. As each record goes through it's production life, in this case
bilogical, they will begin to gain uniqueness. However, in some cases the
uniqueness will only occur at the end of the production line meaning that
the
id and other common info will be its identifier. Does this help?
"Jeff Boyce" wrote:
Anne
I'll assume you wish to use MS Access, which is a relational database.
I'm
having trouble visualizing a situation in which a well-normalized
relational
database table would require a single record to be duplicated.
Can you describe further the issue you are trying to solve by using this
approach?
Regards
Jeff Boyce
Microsoft Office/Access MVP
"Anne" <Anne@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E807515E-C60F-482B-B4DE-230FA8DA31F2@xxxxxxxxxxxxxxxx
I need to be able to write some code for an import or for an append
action
where the importing table has one record of data. In the input form I
would
have a text box where the user would determine the amount of times this
record would be duplicated. It would append to a table where the
primary
key
would be an autonumber ID. I'm not sure if this best handled during
the
import or through an appending process. Assume the importing table has
7
columns of data. Help if you can!
Thanks-
.
- Follow-Ups:
- References:
- Prev by Date: Re: Exporting numbers to csv file-changes format to scientific
- Next by Date: RE: Ask if a memory stick is connected
- Previous by thread: Re: Creating duplicate rows of data based on a determined number of ti
- Next by thread: Re: Creating duplicate rows of data based on a determined number o
- Index(es):
Relevant Pages
|
