Thomas,
Great Info!!!! I have had the same issue since 7.5.00.12 and have just
worked around it and not worried about dbanalyzer.
Today, following your suggestion, I went to MS's website and downloaded
the component checker and found I had MDAC 2.5 SP3.
So, I got MDAC 2.8, installed it, rebooted, and YIPEEE everything is
working.
Thanks for the info,
James
"Koetter, Thomas Theodor" <[EMAIL PROTECTED]>
06/09/2004 09:43 AM
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
cc:
Subject: RE: dbanalyser crash
Hi Tom,
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 9. Juni 2004 10:05
> To: [EMAIL PROTECTED]
> Subject: dbanalyser crash
>
>
> Hi,
>
> after installing maxdb 7.5.0.14 - win32 on a clean win2000
> prof. (SP4) I
> get the following
> error msg:
>
> 1. starting dbmgui on the server-pc itself and connecting to a local
> database causing a memory read error
> "dbanalyzer.exe causes an error ... "
We observed some problems with ODBC on Windows, if an older MDAC
(Microsoft Data Access Components) is used. Installing MDAC 2.7ff
(from MS) solved that problem.
Maybe yours, too.
Regards Thomas
----------------------------------------------
Dr. Thomas K�tter
SAP AG, SAP Labs Berlin
Do you know SAP^H^H^H MaxDB ? www.sapdb.org
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
