Bug #56379 ODBC driver incompatible with Visual FoxPro?
Submitted: 30 Aug 2010 16:22 Modified: 29 May 2013 5:55
Reporter: Steve Austin Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:5.1 OS:Windows (7)
Assigned to: Lawrenty Novitsky CPU Architecture:Any
Tags: ODBC VFP spaces

[30 Aug 2010 16:22] Steve Austin
Description:
    One of the issues is that some field types in MySQL are transcribed as memo fields. Text in these fields has a space inserted after each character in a string, so "Hello" in the database becomes "H e l l o " in the Visual Foxpro remote view. 
    Another problem reported by another user here reports DateTime fields also being transcribed as memo fields.

    So, is this a VFP problem? An ODBC driver problem? Or a mixture of both?

Thanks for your help

How to repeat:
- create new database in VFP
- create a new Remote view on a MySQL table containing VARCHAR and DATETIME field types 
- Browse the results in VFP

Suggested fix:
Have a look at how the ODBC driver works internally
Try to reproduce results on other systems (Excel)?
[31 Aug 2010 7:29] Tonci Grgin
Hi Steve and thanks for your report.

Alas, I see no bug in MySQL SW presented here. The fact that you inserted "Hello" and read back "H e l l o" suggests there is something wrong with your client. Bear in mind that MS does not have such large types as MySQL does, ie. BIGINT, MEDIUMTEXT, VARCHAR ... are all way way bigger in MySQL than any piece of MS SW can handle. So I suggest that you check your table(S) column types before using MS front-end.

There could be a problem with metadata returned by MySQL server for views so you might want to try with ordinary tables and see what's happening.

VPF is quite old piece of SW and I do not have access to it, sorry.

Finally, DSN used should be configured as documented for MS clients.
[1 Oct 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[29 May 2013 5:55] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.