create records automatically

[Guest]

I have a form, formB, that is used and has 4 fields, the exact same fields
that are used in a previous form, formA. The form is requested by users to
review and possibly change the values that were previously selected. formB is
required because the values in formA must be saved for use in a report.

how do i copy the records from formA to formB when it is first created so
the minimal changes can be quickly made instead of re-entering all fo teh
records?

 

[John Vinson]

I have a form, formB, that is used and has 4 fields, the exact same fields
that are used in a previous form, formA. The form is requested by users to
review and possibly change the values that were previously selected. formB is
required because the values in formA must be saved for use in a report.

how do i copy the records from formA to formB when it is first created so
the minimal changes can be quickly made instead of re-entering all fo teh
records?

If you're assuming that data can be stored in Forms, you're mistaken.
Data is stored in tables, and only in tables!

Forms are JUST WINDOWS. If you're trying to edit data in FormB, then
FormB must be based on some table - otherwise you're just moving
pixels around on the screen, and the user's changes won't be recorded
anywhere.

What are the Recordsources of the two forms? What is to be done with
the information in the two forms when the user is done with them?

John W. Vinson[MVP]

 

[Guest]

formA is based on tableA and formB is based on tableB. sorry for the
confusion. i want to copy the records from tableA where social securit number
(SSN) is equal to the specific client of interest. this would essentially put
the same records in tableB. so if there were 5 records copied for the client,
perhaps 1 of them would need to be changed and the other 4 would stay the
same. automatically copying them into tableB would allow for the unchanged 4
records to be present. if they are not copied, then i will have to re-enter
them into tableB, which would take forever.
thanks,

 

[John Vinson]

formA is based on tableA and formB is based on tableB. sorry for the
confusion. i want to copy the records from tableA where social securit number
(SSN) is equal to the specific client of interest. this would essentially put
the same records in tableB. so if there were 5 records copied for the client,
perhaps 1 of them would need to be changed and the other 4 would stay the
same. automatically copying them into tableB would allow for the unchanged 4
records to be present. if they are not copied, then i will have to re-enter
them into tableB, which would take forever.

Well, running an Append query using the SSN as a criterion would be
the way to do it... BUT!!!

Storing the same data redundantly in two tables is almost certainly
not an ideal design. What are TableA and TableB? How do they differ in
design (if at all)? How do they differ in meaning? Why is it
appropriate to have (say) the client name stored in *two different
tables*, so that it becomes much harder to (say) handle name changes?

John W. Vinson[MVP]

 

[Guest]

thanks, i'll try the append query.

sorry i didnt explain it well. tableA is what the customer initially wanted,
tableB is what they actually got.

ie.

TableA - SSN,number_initially_desired,product_name

TableB - SSN,number_customer_bought,product_name

i want to import the matching records from tableA to table B so i can
quickly review the number initially wanted and change it at the time of the
pruchase if it differes from the actual number the are buying, or the if teh
product differs, etc. i dont want to just change the data in tableA because i
have a report that uses the information from tableA and tableB

thanks,
russ

 

[John Vinson]

TableA - SSN,number_initially_desired,product_name

TableB - SSN,number_customer_bought,product_name

i want to import the matching records from tableA to table B so i can
quickly review the number initially wanted and change it at the time of the
pruchase if it differes from the actual number the are buying, or the if teh
product differs, etc. i dont want to just change the data in tableA because i
have a report that uses the information from tableA and tableB

Well...

how about

TableOrder:

SSN, Product_name, QuantityDesired, QuantityBought?

Just leave the quantity bought NULL until you have the data...

John W. Vinson[MVP]