Where to use temporary tables??

[graeme34 via AccessMonster.com]

Hi Could anybody please give me some information?
I am creating a database that contains sales orders, purchase orders,
invoices etc.
Is it best to use temporary tables for data entry, then when all the details
(sales lines) have been entered then update the details to the proper tables
(order and order details). I only ask this as currently when I open a sales
entry form using an autonumber and setting the value of the account index on
the form, all the required fields on the form are complete for the order
table therefore on entering the Order entry form, Access is creating a record
even though I may wish to backtrack on myself. I am still only at the coding
stage (this is a project I'm working on for my degree). Also is it advisable
to use my own incrementing Order Number?
Any advice would be greatly appreciated.
Regards,
Graeme.

 

[tina]

when you have a potential situation where the user may enter data in the
parent (main form) record, move to the subform, and then at some point need
to "void" the data altogether - binding the mainform/subform to temporary
tables is one solution. unless that happens quite frequently, though, i'd be
inclined to go ahead and bind the forms to the "real" tables, and include a
command button on the main form that the user can click to delete the
current record, if necessary.

as far as assigning the OrderNumber yourself, i assume you mean "as opposed
to using the Autonumber data type". the general rule is: if the user is
going to see the value, and especially if it should have meaning to the
user, and/or if it must be sequential - generate it via code. the Autonumber
data type should only be used as a surrogate primary key in a table when a)
the user won't see or care what it is, and 2) its' value is meaningless,
except to the system.

hth