Re: MI MapInfo Compatibility Problems?
Hi Adrian, so I can't see why MI cannot at least allow some backward compatibility. I really feel the same. In my office, there are MI4.1Japanese, MI4.5J, MI5.0J and MI5.5English. MI5.5E can read every Workspace created by both same and lower Japanese versions of MI ...though it cannot show Japanese/Chinese characters properly. MI4.x cannot read Workspaces created/edited by MI5.x(English or Japanese). We usually do not use newer or complicated features of MapInfo but collaboration among different versions of MI is not impossible but VERY FRUSTRATING. I think there are some tools released by third parties, to edit "wor files", such as Workspace Control by an Aussie company. I do not know it can show difference in different versions. I do not see any good reason why in its 'save table as ', and 'save workspace as' options they cannot allow users to choose to save files as older 4.* types not simply as version 2. If Adobe and Microsoft are able to offer this feature with #350 notes software why can't Mapinfo. An extremely reasonable suggestion! ( sorry for my bad English ) I hope you post it on the wish list of MapInfo. Regards, Hiko Kazuhiko Yamashita Division of Environment Marine, Kokusai Kogyo co. ltd 3-6-3 Hakataeki-higashi, Hakata-ku, Fukuoka 812-0013 Japan Phone: +81-92-431-7277 FAX: +81-92-431-7275 -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
Re: MI MapInfo Compatibility Problems?
Yes you are right and why ??? I often simply edit the header info in the tab or wor to downspec the version statement and I can open many new mapinfo files even in 4.1 , 4.1 16 bit (which we use for a few custom mbx's we had built) , 4 for PowerMac and 4.5 so I can't see why MI cannot at least allow some backward compatibility. If you of course are reliant on using some of the more obscure recent line styles improvements, thematic mapping additions or need the over 36,000 node polygons and lines that may fairly well restrict your ability. Welcoming the improvements in linestyle sizes and options in 4.5, we mainly use thematic mapping to alter line styles rather than in the basic data to ensure older versions can remain functional. Since my department budget for software was cut 60% this year I am looking at what maintenance contracts we have, and will be looking at sustaining a variety of version for a few another year since I simply make a bigger rod for my own back each time I upgrade mapinfo and we lose an existing user until this problem is resolved by whatever action. This is making this a real issue to me. I do not see any good reason why in its 'save table as ', and 'save workspace as' options they cannot allow users to choose to save files as older 4.* types not simply as version 2. If Adobe and Microsoft are able to offer this feature with #350 notes software why can't Mapinfo. Is an answer needed! Adrian Can someone please verify that MI 4.1 and 4.5 versions cannot open MI 5.5 tables and workspaces? I have a co-worker in another city that says that 4.1 and 4.5 cannot open 5.5 workspaces and that 4.1 and 4.5 can only open some 5.5 tables. tia steve -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
