Hi, experts.
I am using Access 2003 on XP Home SP3.
I have a MainForm with a TabControl on it with 3 pages. Pages No'2 and No'3 each have their own Subform (let's call them sbfParent1 and sbfParent2). Each sbfParent has its own TabCtl with a sbfChild (1 and 2) on each page. Each sbfChild (we have 4 of them, right?) have a procedure which updates relevant field in MainForm's underlying recordset through a relevant bound textbox in MainForm. Everything is fine until I add and save new record on sbfChild1 and then click on another page of MainForm.TabControl to see a sbfParent2 and its kids. Even before the MainForm.TabControl's OnChange event fires, the entire Access crashes with nice apologies and suggestion to send a report to Microsoft. I decline and try to catch the bug, but so far without success. Could anybody tell me what may be wrong and where to look? Many thanks.
I am using Access 2003 on XP Home SP3.
I have a MainForm with a TabControl on it with 3 pages. Pages No'2 and No'3 each have their own Subform (let's call them sbfParent1 and sbfParent2). Each sbfParent has its own TabCtl with a sbfChild (1 and 2) on each page. Each sbfChild (we have 4 of them, right?) have a procedure which updates relevant field in MainForm's underlying recordset through a relevant bound textbox in MainForm. Everything is fine until I add and save new record on sbfChild1 and then click on another page of MainForm.TabControl to see a sbfParent2 and its kids. Even before the MainForm.TabControl's OnChange event fires, the entire Access crashes with nice apologies and suggestion to send a report to Microsoft. I decline and try to catch the bug, but so far without success. Could anybody tell me what may be wrong and where to look? Many thanks.