Bug #36731 Faulting application msaccess.exe, faulting module myodbc5.dll
Submitted: 15 May 2008 6:28 Modified: 29 May 2013 7:54
Reporter: Egor Klochkov Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:5.1.4.0 OS:Windows (Service Pack 2)
Assigned to: CPU Architecture:Any
Tags: msaccess.exe, myodbc5.dll

[15 May 2008 6:28] Egor Klochkov
Description:
Установлен MS Office Access 2003 версии 11.0.8166.0, MyODBC версии 5.1.0.4 при попытке соединиться через MySQL/ODBC Connector появляется ошибка Faulting application msaccess.exe, version 11.0.8166.0, stamp 46437912, faulting module myodbc5.dll, version 5.1.4.0, stamp 4804d66e, debug? 0, fault address 0x0001790a. Что делать?

It is established MS Office Access 2003 versions 11.0.8166.0, MyODBC versions 5.1.0.4 at attempt to incorporate through MySQL/ODBC Connector there is a mistake "Faulting application msaccess.exe, version 11.0.8166.0, stamp 46437912, faulting module myodbc5.dll, version 5.1.4.0, stamp 4804d66e, debug? 0, fault address 0x0001790a."

How to repeat:
It is established MS Office Access 2003 versions 11.0.8166.0, MyODBC versions 5.1.0.4 at attempt to incorporate through MySQL/ODBC Connector there is a mistake "Faulting application msaccess.exe, version 11.0.8166.0, stamp 46437912, faulting module myodbc5.dll, version 5.1.4.0, stamp 4804d66e, debug? 0, fault address 0x0001790a."
[15 May 2008 7:24] Tonci Grgin
Hi Egor and thanks for your report.

I really can't tell you "Что делать" based on info (not) provided... Maybe to start from MD checksum and check if driver is correct? Also, there are other clients, like MSQRY32 with whom you can test if MyODBC is working at all.
[27 May 2008 15:43] Tonci Grgin
There is a similar report in Bug#37010, hopefully I'll get more feed-back there.
[15 Jun 2008 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[29 May 2013 7:54] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.