[DB-SIG] ODBC and mxODBC

[Bob Kline]

On Wed, 12 Sep 2001, Keating, Tim wrote:

> > > Will it be easy to adapt the wrapper module to handle ODBC as well?
> > > Should I tell my boss to buy the licenses for mxODBC?
> > 
> > I'm biased, so won't comment on this one ;-)
> 
> OK, then I will. When this module went from being free to
> commercially licensed, at first I was pissed. Then I looked at the
> licensing terms, and relative to the cost of other database
> libraries and tools (not to mention the platforms themselves -- for
> example, $40K USD _per CPU_ for Oracle Enterprise!!!), the cost of
> licensing mxODBC is a drop in the bucket. It's a high-quality
> module, actively maintained and support is readily available for a
> reasonable fee.
> 
> Buy the license. It's well worth the $75 USD per CPU.

But first make sure it has the features you need.  The callproc() method
wasn't implemented last time I looked, so you won't be able to work with
output parameters.  Nor was the nextset() method, as I recall.

-- 
Bob Kline
mailto:bkline@rksystems.com
http://www.rksystems.com