RE: MI Workspace Editing : DANGER DANGER
Just amend the line With Highway To With col1 All tables have a column 1. Andrew Hayes GIS Analyst/Programmer Wakefield MDC > Web: http://www.wakefield.gov.uk/ E-mail: [EMAIL PROTECTED] Tel: 01924-(30)5440 Fax: 01924-(30)5424 -Original Message- From: Mats Elfström [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 03, 2000 10:32 PM To: [EMAIL PROTECTED] Cc: Mapinfo List Subject: Re: MI Workspace Editing : DANGER DANGER Hi All! Will Woodruff wrote as a tip for saving wrecked workspaces: > What do I suggest you ask? Replace the problem table with a known table > that will open in both the Open Table section and the Map From section. > Open your workspace. Close the replacement table. Save the workspace. Well, at first this seems as a splendid idea. However, the replacing table cannot be any dummy table. Consider the line Layer 5 Display Graphic Zoom (0, 1500) Units "mi" Label Line Arrow Position Above Font ("Arial",0,9,0) Pen (1,2,0) With Highway Now, if Layer 5 does not contain the column name Highway - the workspace will fail at this point. In fact, it is almost impossible to recognize all references to a missing table in the workspace file. But if the case is a mislaid table, you can give MapInfo a hand in searching: Under Options > Preferences > Directories you can add up to 4 search paths. If you add the 4 most likely drives or trees, MapInfo will traverse each one in turn until a Table with the wanted name is found. Be prepared that this can take a while. Beware that MapInfo opens the first Table found a name that satisfies the search condition. So if multiple tables exist with the same name (no good practice but common nevertheless) another table than the original may well be opened with possibly fatal results. The obvious choice in the workspace opener should of course be an option to skip and turn off all following references to a missing Table. Regards, 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] -- 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 Workspace Editing : DANGER DANGER
For the future, I would suggest our Workspace Manager. Downloadable from our website for a free time renewable version. It can create a .worp file. This in essence is a compressed workspace, that when reopened, can reassign the data files to new directories. You could also archive old workspaces (perhaps those older than 1 year) as a .worp file, then uncompress then in whatever location required. It does require space, as each file making up the workspace is copied and compressed. You can also use Workspace Manager to send whole workspaces to clients, either via e-mail like a .zip or transferring the whole workspace to another storage medium. We often burn to CD or zip drive for easy transfer. It can also parcel the worp file into e-mail bundles for size limit e-mail system. www.empoergeo.com http://www.empowergeo.com/authorized/workspace.htm Here the basics from the readme.txt. Features 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) 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). -Original Message- From: Mats Elfström [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 03, 2000 4:32 PM To: [EMAIL PROTECTED] Cc: Mapinfo List Subject: Re: MI Workspace Editing : DANGER DANGER Hi All! Will Woodruff wrote as a tip for saving wrecked workspaces: > What do I suggest you ask? Replace the problem table with a known table > that will open in both the Open Table section and the Map From section. > Open your workspace. Close the replacement table. Save the workspace. Well, at first this seems as a splendid idea. However, the replacing table cannot be any dummy table. Consider the line Layer 5 Display Graphic Zoom (0, 1500) Units "mi" Label Line Arrow Position Above Font ("Arial",0,9,0) Pen (1,2,0) With Highway Now, if Layer 5 does not contain the column name Highway - the workspace will fail at this point. In fact, it is almost impossible to recognize all references to a missing table in the workspace file. But if the case is a mislaid table, you can give MapInfo a hand in searching: Under Options > Preferences > Directories you can add up to 4 search paths. If you add the 4 most likely drives or trees, MapInfo will traverse each one in turn until a Table with the wanted name is found. Be prepared that this can take a while. Beware that MapInfo opens the first Table found a name that satisfies the search condition. So if multiple tables exist with the same name (no good practice but common nevertheless) another table than the original may well be opened with possibly fatal results. The obvious choice in the workspace opener should of course be an option to skip and turn off all following references to a missing Table. Regards, 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] -- 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 Workspace Editing : DANGER DANGER
Hi All! Will Woodruff wrote as a tip for saving wrecked workspaces: > What do I suggest you ask? Replace the problem table with a known table > that will open in both the Open Table section and the Map From section. > Open your workspace. Close the replacement table. Save the workspace. Well, at first this seems as a splendid idea. However, the replacing table cannot be any dummy table. Consider the line Layer 5 Display Graphic Zoom (0, 1500) Units "mi" Label Line Arrow Position Above Font ("Arial",0,9,0) Pen (1,2,0) With Highway Now, if Layer 5 does not contain the column name Highway - the workspace will fail at this point. In fact, it is almost impossible to recognize all references to a missing table in the workspace file. But if the case is a mislaid table, you can give MapInfo a hand in searching: Under Options > Preferences > Directories you can add up to 4 search paths. If you add the 4 most likely drives or trees, MapInfo will traverse each one in turn until a Table with the wanted name is found. Be prepared that this can take a while. Beware that MapInfo opens the first Table found a name that satisfies the search condition. So if multiple tables exist with the same name (no good practice but common nevertheless) another table than the original may well be opened with possibly fatal results. The obvious choice in the workspace opener should of course be an option to skip and turn off all following references to a missing Table. Regards, 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]
Re: MI Workspace Editing : DANGER DANGER
At 01:50 PM 2/3/00 -0500, ZONING ADMINISTRATOR wrote: >Many have recently responded to problems with opening workspaces due to >deleted or path changed files. ...>What do I suggest you ask? Replace the problem table with a known table >that will open in both the Open Table section and the Map From section. note: It will not necessarily open the workspace if a command in the Layer section of the workspace fails. e.g., labels on a column name that doesn't exist >Open your workspace. Close the replacement table. Save the workspace. It >will now open without the deleted table and you can start to rebuild the >deleted table. I'm not sure if you can recover the data from the recycle >bin, but I would try. Remember that you are looking for a set of files, 4 >or 5 (a file for the tables Indexed fields), being MyTable.TAB, MyTable.DAT, >MyTable.ID, MyTable.IND and MyTable.MAP > >By the way, the order of tables in the Open Table section sets the order of >the list of tables you see when you go to layer control and select Layers > >Add > >William Woodruff >Zoning Administrator >Charter Township of Union, T14 N R4W, Isabella County, Michigan > > >-- >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]