ODBC on W7 and Pharo 1.4

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

ODBC on W7 and Pharo 1.4

Torsten Bergmann
>So to me it seems this is a problem in the ODBC Driver vor Access, but I
>could not imagine that no-one ever have treated Doubles while trying to
>access MS Access with Pharo.

Maybe you should try the newest runtime for Access 2010:

http://www.microsoft.com/en-us/download/details.aspx?id=10910

(for instance in a www.virtualbox.org installation).

to see if it is really a ODBC driver problem.

According to [1] and [2] this should be 15 instead of 53
for SQL_DOUBLE. Correct?

Bye
T.

[1] http://msdn.microsoft.com/en-us/library/windows/desktop/ms716289(v=vs.85).aspx
[2] http://msdn.microsoft.com/en-us/library/windows/desktop/ms711786(v=vs.85).aspx




Reply | Threaded
Open this post in threaded view
|

Re: ODBC on W7 and Pharo 1.4

FDominicus
"Torsten Bergmann" <[hidden email]> writes:

>>So to me it seems this is a problem in the ODBC Driver vor Access, but I
>>could not imagine that no-one ever have treated Doubles while trying to
>>access MS Access with Pharo.
>
> Maybe you should try the newest runtime for Access 2010:
I don't think you can expect that an Access runtime 2010 can
handle an access 2003 application. That's not very likely.

>
> to see if it is really a ODBC driver problem.
>
> According to [1] and [2] this should be 15 instead of 53
> for SQL_DOUBLE. Correct?
Yes.

I tested this result also with an C programm and yes indeed it is 53 and
this is wront. It probably is the number of bit sin the mantissa of a
Double.

A work around may be not to use this query of the column but "hack" it
that it just picks 15 bytes. I guess it tries to load all the 53 bits
and well, who knows what bits pattern there may be around a Double...

Hardly anything meaningful.