Perhaps someone has a solution to this small problem? Further to David Baker's enquiry (28/07) about v1.00 and v3.00 TAB files, I hadn't realised that MapInfo Professional v6.5 insists on saving Copy As.. with the same version (eg, opened v1.00 TAB, will only save as v1.00), and the ONLY way to create "v3.00" TAB files seems to be to export as MIF then import that MIF/MID set again with MapInfo, and finally save to a new dataset name as a TAB.
Though this could be programmed with MapBasic as a batch operation, is there an existing MBX or a standalone utility to upgrade TAB v1.00 to "higher" versions? Ian Thomas GeoSciSoft - Perth, Australia > -----Original Message----- > From: David Baker [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 28 July 2004 10:46 AM > To: [EMAIL PROTECTED] > Subject: MI-L Changing version 1.00 tab files to version 3.00? > > I have a heap of version 1.00 tables - not sure of which version of > MapInfo they were > created with. > > I find that Manifold (another GIS) cannot read these old versions. > However, if I open > these tables in MapInfo 4.5, and then do a "save copy as", they are still > saved as 1.00 > files instead of the normal 3.00 that MapInfo 4.5 would create. So, > Manifold still can't > read the copies. > > One interesting point is that I can manually edit the .tab file with > Notepad, and change > the 1.00 to 3.00 & then Manifold can read them. Only problem is that > MapInfo can't read > them! > > So, any easy way for me to change all my 1.00 tables to 3.00 so that > MapInfo AND > Manifold can read them? > > Thanks, > > Dave > > --------------------------------------------------------------------- > List hosting provided by Directions Magazine | www.directionsmag.com | > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Message number: 12760 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 12819
