Brian Erickson wrote: > I am really confused then. Because according to the ODBC option it will pad > out all my varchars to the full length. That is what is happening right now > is that I have a field that is a varchar(50) on the sever. > CREATE TABLE `Attoserver1`.`testing` ( > `test1` INTEGER UNSIGNED NOT NULL AUTO_INCREMENT, > `test2` VARCHAR(45) NOT NULL, > PRIMARY KEY (`test1`) > ) > ENGINE = InnoDB; > > I run this command select * from Attoserver1.testing > It creates a temp cursor for me. > The structure of the temp cursor is: > Field Field Name Type Width Dec Index Collate Nulls > Next Step > 1 TEST1 Integer 4 No > 2 TEST2 Character 45 > > 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?
-- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" _______________________________________________ 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.
