But..... If I use a view I can specify that the field is a varchar and not a char. Is that something that is inherent in Fox that I am just going to have to deal with. And why did I not have this problem when I was connecting to a mySQl server version 4.1.11????
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek Kalweit Sent: Friday, June 01, 2007 10:18 AM To: [EMAIL PROTECTED] Subject: Re: MySQL ODBC > > The ODBC or fox converted my varchar to a char. That is the problem. > I'm sorry--I must have missed something. What's wrong with it being a > CHAR type on the Fox side? Maybe he doesn't want to incessantly deal with stupid trailing spaces in everything? I don't blame him, but it's an inherent VFP-ism(Dbase-ism)... Bruce, I don't believe VFP's ODBC code supports the varchar -> varchar conversion, as it's older code that existed before the varchar type existed in VFP(added in VFP8 or VFP9, I believe). I think you're stuck with a char() field on the VFP side and you'll be stuck with lots of ALLTRIM()'s, etc. as all my VFP code is forced to use... -- Derek [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 Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
