RE: MI - number of columns

[Trey Pattillo]

Hello,   Is compatible or comparable ?   MI limits each record to 4,000 bytes in any combination of types and up to 250 columns   SmallInt 2 bytes, Integer 4 bytes, float 8 bytes   So it is NOT dBase compatible but comparable as dBase allows over 255 columns and I think 8192 bytes, if not then 4096 bytes   I got a *free* download from ESRI of School District Boundaries......just what I wanted to add to the collection but it would not convert into MI using UT [ yes it has problems but ]   ==>> Error can't open table..........M$ style cryptic message [ WHY NOT ? ]   After opening with Paradox I found that the *.db had over 750 fields ! ! !   Only the first 20 or so had any *real* information then it began with numeric data and column names like MW01, MW02,....MW12, FW01, FW02....FW12, MH01, MH02,....MH12, MW01..................................   Logic jumped in >> Male White 1st grade...12 grade Female White.....Male Hispanic....Female Hispanic   Got any ideas how many of these fields were the *big goose egg* and what year was the data from anyway ! Some of it appeared to even be the cultural breakout of the teachers in each grade........   As a programmer [using Delphi *anit-bloatware*] and data person I learned years ago from M$ that BIGGER IS NOT BETTER, and government still has not caught on that concept either, not to mention a *certain* group of programmer we all kind know -- MI.   Trey Pattillo [EMAIL PROTECTED] http://www.wap3.com