I thought the main point was for you to be able to edit the three fields from the new table (as the pending details should be edited in their respective tables). Please have a look at the new datasheet form frmTempPendingOrders which is based on the design I suggested earlier, every time you open it it refreshes the tempPending table.
Cheers,
Vlad,
Yes that works.. I see the code used in the frmTempPendingOrders
DoCmd.Echo False
CurrentDb.Execute "DELETE tempPending.* FROM tempPending;", dbFailOnError
CurrentDb.Execute "qryAddPendingOrderqry", dbFailOnError
Me.Requery
DoCmd.Echo True
I need to productionize this after a few changes. Please correct my understanding which is as below:
1. The "AddPendingOrderqry", replaces the select query "PendingOrderqry" and this select query created earlier can be deleted
2. The append query only updates the common fields of the Query and the Temptable - The Query has more fields than the Table
3. The Temptable is created by a Query. Correct. Which query?
4. With the QryTempPendingOrder we are linking the tempTable and the additional fields - dates and the Yes/No field of CustpendingTable
5. We display the results of this query "QryTempPendingOrder" in the "frmTemppendingOrders" where we edit the dates and the Yes/No field