 | | | myodbc 3.51 crash | myodbc 3.51 crash 2007-01-22 - By Peter Harvey
Back
Maciej Swic wrote:
> From: Peter Harvey <pharvey@(protected)>
> Sent: 20 Jan 2007 01:10 +01:00
> To: Maciej Swic <m@(protected)>
> Subject: Re: myodbc 3.51 crash
>
> Maciej Swic wrote:
>
>> Peter Harvey skrev:
>>
>>> Maciej Swic wrote:
>>>
>>>> Hi!
>>>> I've created a referee database for use with a card-printer
>>>> software. It can read the database correctly when advancing thru
>>>> records manually using next/prev buttons in the card-printing
>>>> software. However, if i bring up a list of all records in the
>>>> database thru the card-printing-software and double-click a record
>>>> from there, myodbc3.dll crashes the card-printing-app. It is
>>>> possible to browse to the double-clicked record manually but it
>>>> takes a lot of time and this needs fixing. I am probably doing
>>>> something wrong as i havent used mysql with this card-printer
>>>> before. For the record, we are using evolis software.
>>>>
>>>> What could be wrong? I dont know what other info to post so plase
>>>> ask for it. I could also post all the info the windows crash-window
>>>> gives.
>>>>
>>>> Cheers
>>>> MS
>>>>
>>>>
>>> Please consider creating an ODBC trace (on MS Windows use the Control
>>> Panel -> Administrator Tools -> ODBC Administrator). Then look for
>>> any obvious (or perhaps not so obvious) clues to what went wrong.
>>>
>>> --
>>> Peter
>>>
>>>
>> Done, i got a 600kb file full with SQL_SUCCESS. The only suspicious
>> thing i could find were some results contained "BADMEM". I dont know
>> what that means in SQL, could it be time to run memtest86 on the
>> server or client? This database worked without a hitch until Active
>> directory server reinstall. One of the results is below and the entire
>> file here: http://www.maciekish.com/incoming/sql.log
>>
>> eMedia 970-eb0 EXIT SQLSetStmtAttrW with return code 0
>> (SQL_SUCCESS)
>> SQLHSTMT 032D20D0
>> SQLINTEGER 11 <SQL_ATTR_RETRIEVE_DATA>
>> SQLPOINTER 0x00000001 (BADMEM)
>> SQLINTEGER -6
>>
>>
>> Thanks for taking your time!
>>
>>
> The last call to set SQL_ROWSET_SIZE looks suspicious - possibly invalid
> value.
>
> --
> Peter
>
> Hello!
> I have no idea to what that means, im no mysql guru really. Would it be a bug
im the host software or a misconfigured mysql server?
> All worked well until mysql server was reinstalled. Client was untouched.
>
> Thank you again. We are a non-profit org. so mailing lists and forums are my
only options!
>
> Ms
>
> ---- ???Sent using a Sony Ericsson mobile phone
>
>
>
Well it is possible that the client changed via regular MS Windows
updates. MS changes things in the MDAC (the part where ODBC comes in)
regularly and most people either have the updates installed
automagically or do it with a click or two and not realize what exactly
they have just installed. You need to understand, if you do not already,
what layers of software are involved on the client side and try to do
tests which eliminate the possibility of error for each. Usually the
best way to do this is to write C code which simulates what is going on.
In this way you narrow down the problem to specific ODBC calls. The ODBC
trace helps with this.
On the other hand; if it is more to do with the server side then you may
be able to narrow down the problem by submitting the SQL via the mysql
command-line tool.
--
Peter
--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=mysql@(protected)
|
|
|