Hi all,
I developed an application where within one main form 3 subforms are used. 1. Documents, 2. Items within a document, 3. optional Table data if the item represents a table type item. All this is conducted by meta data determining what items should be loaded when a document is created or selected. There is no parent child relation defined between any of the forms/subforms.
The app is used by 80 to 100 users.
For 6 years everything went well.
Since migrated to win7 office 2007, a strange non debuggeable behaviour occurs. When the users switches between a table type item A and another B, as expected each time he clicks on A or B, the 3rd subform shows the data and structure of the related table data as defined by the meta data. When the user clicks inside the 3rd subform, focus is set to the content of that table. Until suddenly, after several switches between table A and B, and clicking again in the 3rd subform, subform 2 triggers, out of the blue, a form.current back to the previously selected table item. When debugging there appears to be no code execution preceding this event. Hence, I have no clou where it comes from. I already checked the app code on simultanious conflicting data access through forms and recordsets. Dirty status is used to avoid pending status of data. I also checked on possible conflicts in naming of public functions and subs, global variables etc. Decompiling, rebuilding by import into a fresh db etc did not resolve the problem.
Does anyone know about something similar related to MsAccess 2007 itself or service packs?
I developed an application where within one main form 3 subforms are used. 1. Documents, 2. Items within a document, 3. optional Table data if the item represents a table type item. All this is conducted by meta data determining what items should be loaded when a document is created or selected. There is no parent child relation defined between any of the forms/subforms.
The app is used by 80 to 100 users.
For 6 years everything went well.
Since migrated to win7 office 2007, a strange non debuggeable behaviour occurs. When the users switches between a table type item A and another B, as expected each time he clicks on A or B, the 3rd subform shows the data and structure of the related table data as defined by the meta data. When the user clicks inside the 3rd subform, focus is set to the content of that table. Until suddenly, after several switches between table A and B, and clicking again in the 3rd subform, subform 2 triggers, out of the blue, a form.current back to the previously selected table item. When debugging there appears to be no code execution preceding this event. Hence, I have no clou where it comes from. I already checked the app code on simultanious conflicting data access through forms and recordsets. Dirty status is used to avoid pending status of data. I also checked on possible conflicts in naming of public functions and subs, global variables etc. Decompiling, rebuilding by import into a fresh db etc did not resolve the problem.
Does anyone know about something similar related to MsAccess 2007 itself or service packs?
Comment