Alex Ross wrote:
>
> Listers,
>
> Our office currently has 4 versions of MapInfo ranging
> from 4.1-5.5. We are having trouble swapping
> workspaces within the department. I was under the
> impression that if you open the workspace in Word as a
> text document you can change the version of MapInfo it
> was saved as. The problem lies in reading back, for
> example if someone saves the wksp in 5.5 any earlier
> version can't read it. I thought we could work around
> it in word as described above. Any information
> regarding a solution to this problem would be greatly
> appreciated.
Hi All.
The obvious solution is of course to synchronize upgrades across your
office.
Any software implemented in this way is likely to cause nothing but
trouble.
Seems as if someone is trying to save a buck but that buck is lost many
times over in time wasted as you run into trouble.
But anyway - a couple of mementos:
1: Do NOT use Word or ANY word processing software to edit workspace
files.
They are pure ASCII and may easily be completely ruined by inadvertently
added formatting codes. Use notepad or a similar tool.
2: MI writes version info into the workspace as needed. I.e. if a
workspace contains commands only valid in 5.5, it will say so. (The same
goes for tables as a matter of fact).
Thus, by changing the version info, earlier MI versions may well be
fooled to read the workspace but will then fail in an unpredictable way
upon encountering the unknown commands.
So to be sure, these commands must be found and removed which may alter
the appearance of the workspace altogether.
Mats.E
--
:::
:Email/ [EMAIL PROTECTED] ICQ#9517386 :
:-:
:Mail/ GISKRAFT, Mats Elfstroem, Vaepplingv 21, SE-227 38 LUND, SWEDEN:
:Phones: +46 46 145959, +46 70 595 3935 :
:::
--
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
