mxODBC chokes on dates! Any Help?

[Owen Ap Owen]

Thanks for the info. It is SQL Server that I am connecting to. But I got 
the same error with date fields when I set up a test connection to 
Access.

It's nice that a fix is in the works. But this seems like something of a 
show stopper (at least for the win32 side of things). 

Considering that the creator of mxODBC is trying to charge a laughably 
exorbitant license fee for commercial use he really needs to fix this 
kind of stuff very quickly. He also needs to add a lot more functionality 
and even then his licensing concept is pretty extreme.


In article <ulmpnnmte.fsf at ctwd0143.fitlinxx.com>, db3l at fitlinxx.com 
says...

> I ran into the same problem with some date fields in an MS SQL Server
> database, and Marc-Andre was able to revert back to an earlier way of
> handling date fields (he preferred a different C data type if defined
> in 2.0.0 than in earlier versions) to resolve it.  I was traveling and
> was a little tardy getting back to verify that the fix worked, but I
> expect it will show up in the next release of mxODBC.