Rx_
Nothing In Moderation
- Local time
- Today, 13:03
- Joined
- Oct 22, 2009
- Messages
- 2,803
Access 2013 has an Application Crash and error that will not fail on Access 2010. Logging this to draw others who might have something like this.
It is also a warning to anyone considering upgrading from Access 2010 to 2013. The application is around 65 MB of forms and complex regulatory code behind the forms with data on SQL Server Linked tables.
Development: Desktop 32 bit Access 2010 - now 32 bit Access 2013 (Both latest SP)
Deployment: Citrix Xen - Citrix has a Server running the same version of 64 Bit MS Access.
On the desktop, a blank Access 2013 DB was created. Imported all objects from Access 2010 version. Set DB Properties to match. Deploy on Citrix 2013.
No problems. Also added conditional compiles for all API calls. No problems.
After around 3 weeks, a random application crash for one single form begin to happen. The Form consist of a Form, Tab Subform and a subform with a lot of rule based form vba.
Note: One PC has Office Access 2010. This form absolutely will not crash on Access 2010 workstation.
The crash can be recreated on the Citrix Access 2013 and Desktop 2013.
Multiple records can be added (one to many). A pull-down field value that is actually the second update to a field in the recordset is consistent in causing the crash. After the crash - the data chosen is actually in the record.
This code was working in a form module for two years. It still works perfectly in Access 2010. It compiles in both Access 2010 and 2013.
Around 50 other forms appear to work fine.
Note: this error can not be trapped. Also, if the code is stepped through in the vba code module, it will not error.
After some other deadlines are complete, more time will be spent including any fix or interesting observation. Perhaps someone searching the internet will find this error and contribute.
Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 15.0.4569.1503
Application Timestamp: 52b0c5f8
Fault Module Name: acedao.dll
Fault Module Version: 15.0.4569.1503
Fault Module Timestamp: 52b0bead
Exception Code: c0000005
Exception Offset: 0000000000032375
OS Version: 6.1.7601.2.1.0.16.7
Locale ID: 1033
Additional Information 1: 431b
Additional Information 2: 431bb22d893c6180b06f244372ea8d2b
Additional Information 3: 79b0
Additional Information 4: 79b057b25e51421c07a75b8e557e209c
Evidently this might possibly be an unresolved issue since July 2014
http://answers.microsoft.com/en-us/...33-25fb8b30ff30?auth=1&rtAction=1456763831740
It is also a warning to anyone considering upgrading from Access 2010 to 2013. The application is around 65 MB of forms and complex regulatory code behind the forms with data on SQL Server Linked tables.
Development: Desktop 32 bit Access 2010 - now 32 bit Access 2013 (Both latest SP)
Deployment: Citrix Xen - Citrix has a Server running the same version of 64 Bit MS Access.
On the desktop, a blank Access 2013 DB was created. Imported all objects from Access 2010 version. Set DB Properties to match. Deploy on Citrix 2013.
No problems. Also added conditional compiles for all API calls. No problems.
After around 3 weeks, a random application crash for one single form begin to happen. The Form consist of a Form, Tab Subform and a subform with a lot of rule based form vba.
Note: One PC has Office Access 2010. This form absolutely will not crash on Access 2010 workstation.
The crash can be recreated on the Citrix Access 2013 and Desktop 2013.
Multiple records can be added (one to many). A pull-down field value that is actually the second update to a field in the recordset is consistent in causing the crash. After the crash - the data chosen is actually in the record.
This code was working in a form module for two years. It still works perfectly in Access 2010. It compiles in both Access 2010 and 2013.
Around 50 other forms appear to work fine.
Note: this error can not be trapped. Also, if the code is stepped through in the vba code module, it will not error.
After some other deadlines are complete, more time will be spent including any fix or interesting observation. Perhaps someone searching the internet will find this error and contribute.
Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 15.0.4569.1503
Application Timestamp: 52b0c5f8
Fault Module Name: acedao.dll
Fault Module Version: 15.0.4569.1503
Fault Module Timestamp: 52b0bead
Exception Code: c0000005
Exception Offset: 0000000000032375
OS Version: 6.1.7601.2.1.0.16.7
Locale ID: 1033
Additional Information 1: 431b
Additional Information 2: 431bb22d893c6180b06f244372ea8d2b
Additional Information 3: 79b0
Additional Information 4: 79b057b25e51421c07a75b8e557e209c
Evidently this might possibly be an unresolved issue since July 2014
http://answers.microsoft.com/en-us/...33-25fb8b30ff30?auth=1&rtAction=1456763831740
Last edited: