It won't make the path's relative, but should solve the problem.
Mike
However, before you go through any more gyrations, you may want to look into
using the Workspace Packager tool to do the actual publishing.
When MapInfo saves a workspace, it always writes the Open Table statements
with relative paths for tables in the same directory as the workspace
itself, or in a directory under that one. It writes the Open Table
statements with absolute paths for tables in other directories. Let's say I
have a mapped drive named T: I create a table at "T:\Foo.tab" and a table
at "T:\Bar\Baz.tab". If I save the workspace into T: the workspace begins
with
!Workspace
!Version 600
!Charset WindowsLatin1
Open Table "foo" As foo Interactive
Open Table "bar\baz" As baz Interactive
But if I save it in My Documents, it begins with
!Workspace
!Version 600
!Charset WindowsLatin1
Open Table "T:\foo" As foo Interactive
Open Table "T:\bar\baz" As baz Interactive
Or, if I used UNC paths when opening the tables,
!Workspace
!Version 600
!Charset WindowsLatin1
Open Table "\\bmc\dfs\temp\foo" As foo Interactive
Open Table "\\bmc\dfs\Temp\bar\baz" As baz Interactive
which insulates you from the vagaries of people mapping different drive
letters.
I'm not really clear on how you're publishing your data and your workspaces
out to the network (I really don't know why you feel the need to work on the
C: drive, but that's for a different discussion). This is going to affect
how you publish the workspaces.
Notice that each Open Table statement has the word "Interactive" in it.
This means if it can't find the table, MapInfo will prompt you for the
correct location. You may have to make re-linking the tables part of your
workspace publishing process.
Besides the Workspace Packager, you could publish a workspace like this:
1. Copy the .WOR file out to the network.
2. Log in from a computer that doesn't have copies of your data on the C:
drive.
3. Open the .WOR file. As it prompts you for the location of each table,
browse to the network location of the network copy of that table.
4. Once the workspace opens itself fully, save it to the final location,
overwriting the "unfixed" copy if you put it there.
Another way is to invest in a text editor like TextPad and create a script
to automatically do the search and replace for you.
________________________________
Spencer M. Simpson, Jr.
-----Original Message-----
From: mapi...@googlegroups.com [mailto:mapi...@googlegroups.com] On
Behalf Of newoptionz
Sent: Friday, May 09, 2008 9:04 AM
To: MapInfo-L
Subject: [MI-L] Making path references relative
| newoptionz <newop...@gmail.com> Sent by: mapi...@googlegroups.com 09/05/2008 14:04
|
|
|
> .
>
>