Hi guys
I have a small but incredibly annoying issue with a form that contains two sub forms on tabs.
Parent form frmJobMaster is based on table Jobmaster which includes a string field JobNo.
Both subforms are based on queries from table JobItems which include linked field JobNo for each item.
On subform 1 I select JobNo, Item, Quantity and Price.
On subform 2 I select JobNo, Item, Condition.
The problem is that if I change a record in Subform 2, then select the tab with Subform 1 get the popup 'Write Conflict' with options to 'Save Record', 'Copy to Clipboard' or 'Drop Changes'.
However if I change a record in Subform 1, then select the tab with Subform 2 everything is fine.
I have included
If Me.Dirty Then DoCmd.RunCommand acCmdSaveRecord
in OnLostFocus, OnDirty and AfterUpdate events on both subform and refresh everything in the Tabbed Supforms Change Event but still keep getting this prompt and despite 3 days searching the Internet cannot find a may to avoid this message, or effectively trap it and provide a default answer.
:banghead:
Has anybody got a workaround for this?
I have a small but incredibly annoying issue with a form that contains two sub forms on tabs.
Parent form frmJobMaster is based on table Jobmaster which includes a string field JobNo.
Both subforms are based on queries from table JobItems which include linked field JobNo for each item.
On subform 1 I select JobNo, Item, Quantity and Price.
On subform 2 I select JobNo, Item, Condition.
The problem is that if I change a record in Subform 2, then select the tab with Subform 1 get the popup 'Write Conflict' with options to 'Save Record', 'Copy to Clipboard' or 'Drop Changes'.
However if I change a record in Subform 1, then select the tab with Subform 2 everything is fine.
I have included
If Me.Dirty Then DoCmd.RunCommand acCmdSaveRecord
in OnLostFocus, OnDirty and AfterUpdate events on both subform and refresh everything in the Tabbed Supforms Change Event but still keep getting this prompt and despite 3 days searching the Internet cannot find a may to avoid this message, or effectively trap it and provide a default answer.
:banghead:
Has anybody got a workaround for this?