SQL-SELECT against View via ODBC?

[Bill Seitz]

I established that the "cause" of the problem is that one of the
tables in my view has a Text field. It's the last field in the base
table, so those queries always worked fine. When I built the view, it
was no longer the last field, so the error reared it's ugly head.

Does anyone know whether mxODBC has this bug? The person who led me on
this discovery thought so, but wasn't too sure...

Also, I'm not clear on what qualifies as "commercial" use triggering
the non-free status of mxODBC? Is it limited to using the API within a
product for sale, or does any internal use by a corporate trigger it?

"Steve Holden" <sholden at holdenweb.com> wrote in message news:<2l%Z6.22470$g4.740189 at e420r-atl2.usenetserver.com>...
> The generic odbc driver (I presume you mean the one from the Windows
> extensions) is known to be in need of maitnenance, and I understand from a
> recent posting that Mark Hammond expects to release a slightly updated copy
> (may even have done so by now).