>Yeah, there's lots of options, and it's worth looking at what your >version of VFP is expecting and how you want the various types of >fields to be translated.
I was aware of the options, but I had always used the MySQL ODBC GUI to set them up, I hadn't realized you could put that in as part of the Connection String, which is cool, since mucking with GUI settings is a pain for deployment to each client machine. >Sorry, thought the code was clear: you set lcDatabase to 'test' but >then included the name of the test database directly in your >connection string. I substituted the lcDatabase string. DOH!!! (Homer Simpson style) - Thanks for pointing it out. >Define "proper." > >Run the first time, I saw, ID I(4,0), T C(0,0), MT C(0,0) and LT >C(0,0), which is what I would expect. At first I couldn't understand why you'd think this is the proper result, but thinking it through, if odbc is trying to optimize the size of the columns, and there's no data in there, I can see why a C(0) would be your expected result. I've always used the "Don't Optimize" setting (since Whil said to in his book), so to me the "proper" result should always be ID I(4,0), T M(4), MT M(4), LT M(4) >Adding the OPTION clause above resulted in: ID I(4), T M(4), MT M(4) >and LT C(255), which is an interesting result. Yes, that is the "bug" I've been referring to. The LT field should not be a C(255). In really old versions of the MyODBC Driver, such as 3.51.06 for example, the returned results are as expected, ie, Memo for all 3 text type fields. Unfortunately, 3.51.06 doesn't play very nicely with MySQL 5, and any driver that does, has the bug. >And commenting out the drop command confirmed that the data was being >saved properly. Yes it does save it properly, but the critical question, and the reason I noticed this bug in the first place, is, that you'll find reading the data back from the LONGTEXT field will truncate your results to (you guessed it), C(255).. >So, in this case, it appears the ODBC may be failing to properly >interpret the sizes of the fields. I would concur. Do you know the best method to report this bug to be fixed quickly as a conversion I'm doing requires a LONGTEXT field? Thanks _______________________________________________ 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.
