Creating a new record based on another table

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I want to create a series of records in a table using values from another
table. Ideally I would like to loop through all the records in one table and
add values in another - is this reasonably straightforward - I'm very
inexperienced at programming and would appreciate any advice
 
Peter,

This sounds like a job for an Append Query or an Update Query.

Please post back with more details, perhaps with exampes, of what you
are trying to do, if you need more specific help with this.
 
While you can do this, you might want to post more details. This sounds
like you will be duplicating information which is not advised in a
normalized database structure. Instead, you should create a relationship
between your new table and any existing tables which contain related data.

Without more information, it would be hard to tell you which way would work
in this instance. Please post a little more detail.

Thanks,

Rick B
 
Hi Steve
I have a table of standard tasks generally associated to a job and another
table of tasks which will be associated directly to the job which may not be
simply the standard tasks - to save time I was hoping that all the standard
tasks from the tblStandardTasks could be created with a unique job no
collected from an entry form to tie them to the job - fields in the
tblStandardTasks would be description of the task and the amount of days
before the job is fitted that the task would be scheduled for. I could then
use this info to fill in the task description and date field in tblTasks.
Hope this makes it a little clearer.
 
The purpose of the tblStandardTasks would be used only to quickly populate
the tblTasks - I would envisage perhaps only 10-15 items in this table - the
only duplication in the tblTasks would be the description field - I was not
proposing to link the tables - each task in tblTasks would have it's own Id
and a specific date and job allocated to it - does this make any more sense?
The whole purpose of the database would be to manage a series of tasks
related to a job - all jobs would have a collection of 'standard' tasks but
would also have some tasks which were unique to that job.
 
Peter,

Sure. In that case, all you need is run an Append Query every time a
new Job is created, to enter the relevant data from the StandardTasks
table, along with the JobNo of the new job.
 
Back
Top