J
John Watson
I've been trying to implement the subform transaction example from Acccess
2K Dev. Handbook Ch. 8 but it seems to be incomplete or I'm missing
something. The code and logic for calling ResetData() works fine when
updating existing records but falls down when adding a new main form record.
During ResetData, the attempt to assign the querydef recordset as the source
causes a 3314 error on the main form. It seems as though the empty parent is
instantiated on the form (showing the new autonumber to be assigned) and
then focus is moved to the subform when assigning the recordset which is
triggering the error.
Has anybody tried this example or know what I am missing?
Thx,
John
P.S. My workaround is to hide the subform during Add mode and then
reposition to newly added record for update which then makes the subform
visible. At this point, any updates/adds to the subform are controlled by a
transaction.
2K Dev. Handbook Ch. 8 but it seems to be incomplete or I'm missing
something. The code and logic for calling ResetData() works fine when
updating existing records but falls down when adding a new main form record.
During ResetData, the attempt to assign the querydef recordset as the source
causes a 3314 error on the main form. It seems as though the empty parent is
instantiated on the form (showing the new autonumber to be assigned) and
then focus is moved to the subform when assigning the recordset which is
triggering the error.
Has anybody tried this example or know what I am missing?
Thx,
John
P.S. My workaround is to hide the subform during Add mode and then
reposition to newly added record for update which then makes the subform
visible. At this point, any updates/adds to the subform are controlled by a
transaction.