Please Help

[pame1a]

I am using VB to create my front end and SQL Server 2000 for the db.

I have created four forms, which recieve data from the user, each form is directly linked to an individual table in the sql server 2000 db. (I am creating a system that creates car contracts- 1st form recieveces customer details, next form recieves car details etc. The last form confirms the contract has been successful.) The way I had it before is that the each table is updated as the user completes each form. However, I later realised this is not a sufficcient way since the user may decide to abort the transaction half way through filling the pages. Therefore, some table will be updated (with information that is no longer needed) while some will not have been changed. The data should only be transferred to the database on the last confirming form.

What I have done now is used a disconnected recordset which saves the data in the client side, and my plan was to transfer the information into the database after all forms had been completed. Problem is, how do I input that data into seperate tables. I have created a view that links all the tables together. Can I just update the view? How do I know if it is a updatable view?

Another way I thought may work is by creating a recordset for each form (ie a recordset for each individual table in the db) and then transferring the data to the db at the last form by having a batchUpdate for each table. Is that possible?

PLEASE HELP

[Ecniv]

Is this networked?


Possible options...
1)
Storing the comp ID (as each person on a comp can only enter one record at any one time) in each of the records.
If Cancel is pressed, run four delete queries using the comp ID and check against a status.
On confirm, set the status to confirmed using four update queries.

2)
Have a mimic of the tables, which hold the data (and can be cleaned out at the end of each day) entered until confirm, which saves the data to the mimic then saves all mimic to the main db.

3)
Not too good but use a tab on the form, with the Confirm/Cancel on the last tab. Then only need to store once the confirm is pressed. Uses way way way many controls, but you can add validation etc on the confirm press, so it doesn't save until all data entered is correct.

Just come possibilities I dreamt up now


Vince

[pame1a]

im only creating a prototype so will only be presenting on the 1 computer? How do I create mimics......is a disconnected recordset similar to this???