G
Guy Sohmbadi
- Clean Install Windows Server 2k3 w/SP1
- Install Office 2k3 (COMPLETE!)
- Install all Updates for Windows & Office. (Office SP1 etc.)
- install MySQL ODBC Connector, v 3.51.12
- create a "System DSN" to a mySQL database & "test" it. (it will work, obv.)
- open access 2k3, and create a new DB.
- under "File" go to "Get External Data" and choose ODBC.
- in the ODBC window, choose your newly created mySQL connector
- Click OK.
**ACCESS CRASHES**
- Wash, rinse, repeat!
This same crash occurs on a fully-patched win2k install with office 2000 as
well.
The sad thing is, it was working WONDERFULLY until some RETARDED DEVELOPER
broke the damn thing with a service pack.
I know this to be the case because if I replace msjet40.dll with an older
version, the problem goes away. Of course, windows file protection replaces
the damn thing with the latest version of msjet40.dll every time I reboot.
so, this "fix" quickly loses its lustre.
Please beat the coder with a clue-by-four, then fix this bug.
- Install Office 2k3 (COMPLETE!)
- Install all Updates for Windows & Office. (Office SP1 etc.)
- install MySQL ODBC Connector, v 3.51.12
- create a "System DSN" to a mySQL database & "test" it. (it will work, obv.)
- open access 2k3, and create a new DB.
- under "File" go to "Get External Data" and choose ODBC.
- in the ODBC window, choose your newly created mySQL connector
- Click OK.
**ACCESS CRASHES**
- Wash, rinse, repeat!
This same crash occurs on a fully-patched win2k install with office 2000 as
well.
The sad thing is, it was working WONDERFULLY until some RETARDED DEVELOPER
broke the damn thing with a service pack.
I know this to be the case because if I replace msjet40.dll with an older
version, the problem goes away. Of course, windows file protection replaces
the damn thing with the latest version of msjet40.dll every time I reboot.
so, this "fix" quickly loses its lustre.
Please beat the coder with a clue-by-four, then fix this bug.