🚀 go-pugleaf

On Fri, 7 Dec 2001 18:25:01 +0800, Liu Haizhou <zeroliu@163.com> wrote:

>
>Hi!
>
>I want to access MySQL database via MyODBC and ADO components. I've 
>setuped the ODBC as MyODBC required, i.e., checked the "Don't optimize 
>column widths" and "Return matching rows" options. But I faced a very 
>strange question: C++ Builder cannot identify the MySQL's varchar field 
>type. 
>I wanted to add fixed fields to the ADOTable or ADOQuery component. So I 
>chose "Add all fields", some VARCHAR fields were distinguished as 
>"TStringField", at the same time, the other were "TMEMOField". All of 
>these occured in the same table. I've tried many times, but these didn't 
>changed. I really don't know why.

I've noticed that MyODBC fails to return correct types (it exchanges string
fields with memo fields) when the returned recordset (relation) is an empty
set.  

AFAIK, a possible workaround is to check, upon the opening, whether the
DataSet's EOF flag is true. If it's true you can't make any access using
(directly or indirectly) DataSet's fields.

HTH

Ciao!

Giuliano