mySQL 5.0.24a, ODBC 3.51.12, VFP9 SP1

A mySQL table defined thus:


CREATE TABLE "test" (
   "Atext" text NOT NULL,
   "Avarchar" varchar(45) NOT NULL,
   "avarbin" varbinary(45) NOT NULL
);

and VFP SQLCOUMNS gives:
atext  Memo
avarchar  char(45)
avarbin     char(45)

NOTE that it does NOT translate the mySQL varchar and varbinary properly, 
but TEXT is OK

SQLCOLUMNS with the NATIVE call gives shows avarchar and avarbin both as 
varchar(45) and the same SQL data type (12). Not good!

Looking at the mySQL INFORMATION_SCHEMA.COLUMNS table for this table shows 
avarbin as varbinary(45) .

The problem must be in ODBC or in VFP - maybe I can try using ACCESS to 
look at the table and see what it says. It will also use ODBC, so if it 
shows the proper type, then VFP is to blame.

I was burned by this since I was trying to use a VARBINARY to store 
encrypted data, and I had to manually define the remote view for the table 
so I could set the field property properly.

Something weird here.

Larry

At 12:01 AM 3/1/2007 -0500, you wrote:
>I've been having all kinds of trouble writing some generic code to
>create remote views programmatically from a MySQL 5 database, and I
>believe I've narrowed down the problem, and wanted to see if anyone
>else has seen this and has a workaround..
>
>When I a create remote view programmatically, any fields that are
>TEXT fields in MySQL 5 are coming back as C(0)..
>
>I confirmed this infact using SQLColumns(handle,"FOXPRO"), which
>indeed shows C(0) as the type for all the TEXT fields on the backend.
>
>This surely is a bug, but is it a VFP bug, a MySQL bug, or an MySQL ODBC bug?
>
>What can I do to work around this? Has anyone else seen this problem?
>
>Thanks-
>Steve
>
>
>
>
>
[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to