mxODBC chokes on dates! Any Help?

[Penfold]

"Owen Ap Owen" <no at thank.you> wrote in message
news:MPG.152e9338351a7e1b9896a7 at news.pacbell.net...
> 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.

Considering lots of developers in commercial settings such as finance and
banking
currently free ride off what is in general a fantastic package, its not that
laughable.

Questions:
(i) Did you try to contact him directly ?  He has always been very prompt in
replying
to me when I have, and I do *not* pay him a licence fee
(ii) Have you actually paid any money for mxODBC.  If not, why do you expect
that it
should be perfect and that he should fix it for you quick smart if it aint ?

I imagine you probably think that mxODBC and mxDateTime, a fantastically
useful package
as well, should be free for you to use and abuse simply because you expect
to be paid to
do development work for a commercial company, but you think that others
should provide
for free the tools you need in such work.

If its a problem, why not write your own DB interface and datetime support,
I'm sure you could
manage it in a jiffy ;-)

>
> 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.