Most database designs do not function well with that many columns, even if it is possible.
Here is a small chunk of your column definitions: `ACCHG` double(18,4) default '0.0000', `ACCHG_DC` int(2) default '0', `ACCLI` double(18,4) default '0.0000', `ACCLI_DC` int(2) default '0', `ACCO` double(18,4) default '0.0000', `ACCO_DC` double(18,4) default '0.0000', `ACDO` int(2) default '0', `ACDO_DC` double(18,4) default '0.0000', `ACO` int(2) default '0', `ACODO` double(18,4) default '0.0000', `ACODO_DC` double(18,4) default '0.0000', `ACOMINC` int(2) default '0', `ACOMINC_DC` double(18,4) default '0.0000', `ACOX` int(2) default '0', `ACOX_DC` double(18,4) default '0.0000', `ACO_DC` double(18,4) default '0.0000', `ACQDISN` int(2) default '0', `ACQDISN_DC` double(18,4) default '0.0000', `ACQDISO` int(2) default '0', `ACQDISO_DC` double(18,4) default '0.0000', It appears to me that you have groups of related values (the ACC group, the ACD group, the ACO group, etc). I believe that everyone would agree with me that you should seriously consider normalizing your data. Why did you not consider one table per group? What was your need to keep all of your data in the one row? Puzzled, Shawn Green Database Administrator Unimin Corporation - Spruce Pine "Filip Wuytack" <[EMAIL PROTECTED]> wrote on 10/05/2004 09:25:32 AM: > Hi, > > I'm trying to create a table that has > 1000 columns, but I keep on getting > Error Code : 1005 (errno: 139). Does anyone has an idea why this happens? I > thought the limit in number of columns was around 3500... > > Many thanks, > > Filip > > I've attached my sql statement as a zipped file as otherwise my email got > big and was rejected by your mailinglist server. > > > > [attachment "sql_innodb.zip" deleted by Shawn Green/Unimin] > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] >