I think I figured this out. Turns out that it was not the number of fields I had (225) but instead was simply the amount of data that "adds up" into a single record. I had one particular record that was "full" on just about every field (in terms of length), and when I eliminated that one single record, everything worked fine, even with 225 fields in the table. The problem was "record length" not the number of fields.
Thanks to everyone who responded. Frank -----Original Message----- From: Phillips, Frank [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2003 9:44 AM To: 'MapInfo-L' Subject: MI-L Limit on Fields in an MDB? This question has probably been asked a million times, but I'm going to ask it again: Is there a limit to the number of columns/fields in an Access file (MDB) that MapInfo can read? I just tried to open a table in an MDB where the table has 225 fields and got an error. Frank Phillips Manager of Marketing GIS Vulcan Materials Company (NYSE:VMC) Birmingham, AL, USA --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 7689 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 7707
