A qick comment - Workspace Manager cannot handle seamless tables.
Christopher Prescott
Geospatial International Pty. Ltd.
14 Wheaton Road
Evandale
South Australia 5069
Phone: +61 8 8362 3278
Mobile: 0417 856 109
email: [EMAIL PROTECTED]
-----Original Message-----
From: Alistair Hart [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 6 January 2000 15:40
To: [EMAIL PROTECTED]
Subject: MI Summary: Workspace Management Tools
Thankyou to the people who responded to my request for information/software
relating to the transport of Workspaces.
Below is a summary of the responses:
4th Beach Software from Melbourne (Aust.) have an inexpensive utility called
Workspace Control.
Exa-Min in Brisbane (www.geobasemap.com) have an application called
Maplinker which does a number of great things like linking Mapinfo datasets
to all sorts of external data sources, and stores map objects in a database
that replaces the Mapinfo Workspace. The database will actually track files
that have been moved from one directory to another and repair any broken
links created by files being moved or deleted. It also improves management
of metadata and lets you organise maps in a hierarchal structure which can
be really useful even for small projects.
CopyPlus and SearchPlus from SpatialPlus (apparently now extinct!).
CopyPlus is a relatively simple program that runs independant of MapInfo and
allows the transfer of Workspaces to different directories/CDRoms and also
allows the conversion from MI5.5 back to MI5.0
Workspace Manager is designed to facilitate easy management and distribution
of a standard MapInfo Professional(r) Workspace file (.WOR extension).
Version 1.0 of Workspace Manager has been tested with MapInfo Professional
v4.5 and v5.0. (and 5.5 - Sinam)
Workspace Manager is from empowergeo
(www.empowergeo.com) and it seems pretty good.
Following are some of it's features.
a) Resolves missing/relocated .TAB files.
You can let Workspace Manager search drives for you automatically, or you
can specify a particular file replacement.
b) Workspace Packages (.WORP) can be built to send a Workspace to another
user via disk, email or other electronic transport mechanism.
The Workspace Package can include any or all of the tables that are used in
the Workspace (within the Limitations listed in IIa). The Packaged files
are compressed to reduce disk space and transmission time requirements.
c) The recipient of a Workspace Package would use Workspace Manager to save
the enclosed Workspace and Tables to disk, and will assist in the location
of any tables not included in the distribution.
d) Workspace Manager will default to extract only newer Tables from the
Package thus preserving your local copies as appropriate. The user can
easily override this default on a Table by Table basis.
e) There is no physical restriction on the number of Tables that can be
included in a Package or on their sizes (within available disk space
requirements for building or extracting them).
I hope this helps anyone else that may be wondering whats around.
Regards,
Alistair Hart
Qld Health
[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]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
