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. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ellenoff Sent: Friday, June 01, 2007 8:40 AM To: [EMAIL PROTECTED] Subject: Re: MySQL ODBC Make sure the following in your mysql odbc advanced settings are turned on/checked: flags 1: Don't optimize Column Width flags 2: Pad Char to Full Length Most likely the "Pad Char to Full Length" should fix your problem with varchar fields. Not sure why the view would blowup after in-activity. At 10:16 AM 6/1/2007, Brian Erickson wrote: >I am having a very big problem with the way Fox is interacting with the >MySQL odbc driver. Below is the connection string that I am using to >connect to my db server. There are a couple of problems that I am running >into. >1. In a sql pass through any of the varchars on the server are coming >through as a char. That is not a problem the problem comes when I connect >the cursor to the backend server make a couple of changes and push updates. >All of the character fields get padded out with spaces. That is inflating >the db and causing problems with indexes and locate statements. >2. If I open up an actual remote view and not use sqlexec() and not do >anything with the view for an amount of time then try to close the view I >get a fatal odbc error. SQL Server has gone away error number 2006. > >I have looked on line for some resolution but have not found any. >Server version: 5.0.32 >Driver version: 3.51.15.00 and 3.51.12.00 I have the same problems with >both versions. > >Is there any way to get the padding to sop and the disconnect to stop as >well????? > >DATABASE=atto;DRIVER={MySQL ODBC 3.51 >Driver};OPTION=2057;PWD=*****;PORT=3306;SERVER=*******;UID=******* > > > >No virus found in this outgoing message. >Checked by AVG Free Edition. >Version: 7.5.472 / Virus Database: 269.8.6/828 - Release Date: 6/1/2007 >11:22 AM > > > >--- StripMime Report -- processed MIME parts --- >multipart/alternative > text/plain (text body -- kept) > text/html >--- > [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.
