Further to the last message (below) I discovered that there probably IS an incompaibility with Integer fields. I found that my dBASE converted table had a field format of Numeric (10,0) instead of Integer, when converted by MI (and not my prog). So I ensured my converted table had this format and there is no problem now. Still beats me WHY though - something to do with the relative numerical ranges of integer fields between the 2 systems? Terry McDonnell
________________________________ Hello Listers I have a Foxpro tablen which has been, some time in the past, converted to a dBASE .DBF file and imported into and converted to an MI file. On starting my MB app the table is registered as below: Register Table gcWADPath + "SerData\RZStop.dbf" TYPE DBF Charset "WindowsLatin1" Into gcWADPath + "MapData\RZStop.TAB" Open Table gcWADPath + "MapData\RZSTOP.TAB" Interactive Now, recently I have had to alter the structure of my Foxpro table, adding extra fields, but none that I would expect to be "alien" to MI/MB (V 7.8). I've added more of the same character and numeric fields as were always there but one field as INTEGER. When the prog gets to the "Register" command above I get the error message: "This table contains unsupported field types. .... Unable to prepare table ..." Now I'm a bit rusty on the process to make the dbf table compatible so perhaps you could advise me if I've missed something out but I: * took the new version of my Foxpro table and converted it to dBASE. * opened it as a dBASE file in MI, code page convert it, etc., with the MB window open, which resulted in the following code: Register Table "C:\mcl_windows\MapData\rzstop.dbf" TYPE DBF Charset "WindowsLatin1" Into "C:\mcl_windows\MapData\rzstop.TAB" Open Table "C:\mcl_windows\MapData\rzstop.TAB" Interactive Map From rzstop and a map window opens up OK. Note that, apart from the paths, the syntax above is the same in my prog. I'm able to browse the table (although it's empty at the moment). As soon as I run my prog again I get the same error message. What gives!? And are dBASE integer and MI integer fields incompatible? Surely this would be documented?! Can anyone help please? Terry McDonnell
