Hi Users
Coincidentally, there were two issues posted regarding workspace "stability". Thanks
to all that answered my question. Special thanks to Dennis Waardenburg, he nailed the
question
Here it is:
"
In a word, no. If you have moved or deleted files referenced in a
workspace, the workspace will stop opening at the point it encounters a
reference to the missing file. If the files are simply in a different
location, either move them back to where the workspace expects them, or open the
workspace file in a text editor and change the path in its "Open Table" statement. If
the file has been deleted, the only thing you can do is open the workspace file in a
text editor and remove all references to the missing file(s). This can be difficult,
as you must remove the "Open Table" statement for the file, any queries ("Select From"
statements) made from the file, and all references to the file in the "Set Map", "Map
from", "Shade", etc. statements.
....
Dennis Waardenburg
GIS Specialist
The Environmental Company, Inc.
<[EMAIL PROTECTED]>
"
I will place my scenario hoping MI Corp is reads it and does something to change this
awkward limitation.
We received from a client a neat database. All are forest cover digital maps in IGDS
format . For this project 106 digital mapsheets were translated splitting it into 60
layers of information per mapsheets. From these, I selected 13 relevant layers.
106 Maps translated into 13 final layers.
The client wants four mapsheets per layout:
106/4 = 26.5 layouts But to adjust the maps for those adjacents, the number of layouts
required is 31.
Each layout has to have:
Four mapsheets and each mapsheet has 13 layers so 52 layers (TAB) files have to be
opened, themed and framed into a map layout.
Catch:
The translation process from IGDS to TAB/SHAPE is fine but sometimes, one layer or two
don't show up. Some of them for good reason for instance: The "lakes" layer.
If the mapsheets area is in a place with no lakes, there won't be this layer. This
process goes on and on. Always some layers will be missing due the database own nature.
Do by hand the "open" and "close" statements, themed them all and place the final into
a layout is time consuming and not much clever.
52 layers / layout times 31 layouts gives 1612 basic open statements.
So, I decided to create a template workspace based on by hand complete mapsheets
layout and use it as a files input for a simple VB program. The same program reads
another file with the set of the remaining mapsheets names. It replaces the original
mapsheets by the new mapsheets variable. replicating all 1612 minimum commands in on
second.
The problem with missing layer in the *.wor was always well known and the basic
editing the workspace approach is a way to get around this situation. However, facing
the number of layers and the amount of commands needed, I hoped by now somebody of
even MI Corp would have an alternative solution.
Unfortunately, for now, the only solution is to replicate mapsheets and layers by
cloning all missing data by a set (template) of complete layers even if this
template is out of layout frame. It won't appear in the layout anyway and it will
comply with all MB instructions set in the workspace template since the data structure
is the same.
Note from Jason:
... If the exact table is unavailable, just pick one that has a similar structure.
I think that's the best you can do unfortunately.
Jason Adam <[EMAIL PROTECTED]>
"
Another solution is to move to AV where if a layer is missing it disregards any
procedure that mentions the missing layer. But this is another story.
This seems a desperate solution for this extensive database.
Thanks for all that replay
Dyan C. Catamaran
Phero Tech Inc.
--------------------------
604-940-9944
604-940-9433
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
