If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Unanswered: pre-populate a form from one table but saving it into another

Hi,

I need advice on how to go about pre-populating fields on a Form from one table, allowing changes to be made and then saving these entries on a second table.

Eg I need 'FormA' to load on a click event, pre-populated from 'Table1', Users can then make any changes to this pre-populated form (without changing the source data in 'Table1') and then click the Email button. On clicking the Email button I want the data in the Fields to be save into 'Table2'.

Have a 'working' table, default table, and final table.
User clicks edit, it runs append query to the 'working table'
all defaults are appended from the 'default table' to an empty 'working' table that the form is connected to.

The user then edits the 'working table' when done, click ths SAVE button.
The save button runs another qry to append the changes to the 'final' table.

why would you you DUPLICATE a table, let alone TRIPLICATE it... unless there are very very good business reasons to do so its a recipie for disaster.
instead consider having a state column which tells you what state that row is in (ie working, default or final)
why.. well its juts pants to store the same data more than once. but there is a good reason not to. ...what happens if some bright spark decides to have a 4th 'table', called say 'production'.. in your model that means creating a new table, modifying queries, modifying forms and so on... the state flag way means that another state can be handled seemlessly without further development time or resource.