Steve, When MI crashes it comes up with a Dr Watson error with the following
message:
An application error has occured and an application error log is being
generated
MAPINFOW.exe
Exception: access violation (0xc0000005),Address: 0x027960d0
The happens as soon as I click on OK to open the data source (which works
fine in Access etc)
Following is the output from the odbc log file:
----------------------------------------------------------------------------
-------------
Mapinfow 9c:da ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x00000000
SQLHANDLE * 0x01f02c30
Mapinfow 9c:da EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x00000000
SQLHANDLE * 0x01f02c30 ( 0x01f11440)
Mapinfow 9c:da ENTER SQLSetEnvAttr
SQLHENV 0x01f11440
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000002
SQLINTEGER 0
Mapinfow 9c:da EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x01f11440
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000002 (BADMEM)
SQLINTEGER 0
Mapinfow 9c:da ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x01f11440
SQLHANDLE * 0x01e6f7e0
Mapinfow 9c:da EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x01f11440
SQLHANDLE * 0x01e6f7e0 ( 0x01f114e8)
Mapinfow 9c:da ENTER SQLSetConnectAttr
SQLHDBC 0x01f114e8
SQLINTEGER 1998 <unknown>
SQLPOINTER [Unknown attribute 1998]
SQLINTEGER -6
Mapinfow 9c:da EXIT SQLSetConnectAttr with return code 0
(SQL_SUCCESS)
SQLHDBC 0x01f114e8
SQLINTEGER 1998 <unknown>
SQLPOINTER [Unknown attribute 1998]
SQLINTEGER -6
Mapinfow 9c:da ENTER SQLDriverConnectW
HDBC 0x01f114e8
HWND 0x00ac026c
WCHAR * 0x1f4be068 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1f4be068
SWORD 8
SWORD * 0x00000000
UWORD 1 <SQL_DRIVER_COMPLETE>
----------------------------------------------------------------------------
-------------
Don't know if this makes it any clearer.
TIA
Richard
----- Original Message -----
From: MapInfoL <[EMAIL PROTECTED]>
To: Richard Waters <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, July 19, 1999 9:32 PM
Subject: Re: MI ODBC Crashes
> Hi Richard,
> It would help to know what you mean by crashes. Does it GPF, if so what
> module?
> Usually it is down to the ODBC driver not being capable of what MapInfo
> requires.
> You can turn on ODBC logging in the ODBC section of control panel. Check
> the logs to see if you get any further into.
> Hope this helps,
> Steve
>
>
> -----Original Message-----
> From: Richard Waters <[EMAIL PROTECTED]>
> To: Mapinfo Mailing List <[EMAIL PROTECTED]>
> Date: 19 July 1999 02:33
> Subject: MI ODBC Crashes
>
>
> >Looking through the mapinfo-l archives it seems that there are a number
of
> >people having problems with MI crashing whilst connecting to ODBC
> databases.
> >I posted a question a couple of days ago about this but have not had a
> >response yet. I am using MI 5 and NT4 SP5 on a newly built machine. I
have
> >been using the Relativity ODBC tool to connect to Cobol databases on a
Unix
> >server.
> >
> >TIA
> >Richard
> >_________________________________________________________________
> >Richard Waters <[EMAIL PROTECTED]>
> >Information Technology Manager
> >Wentworth Shire Council <[EMAIL PROTECTED]>
> >Tel (03) 5027 3203 Fax (03) 5027 3082
> >
> >----------------------------------------------------------------------
> >To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
> >"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
> >
>
> ----------------------------------------------------------------------
> To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
> "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
>
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
