>> i'm trying to open up this workspace, and get the following error.
>>
>> (R:\...\....\....\broc.wor:150) Invalid style value 0
>>
>> What does this mean? Altering this value in the workspace doesn't
>> correct it, so what will?
>Your wor was generated with a MI version prior to 4.5 and you are
>using it with a version 4.5 or more recent.
>
>4.5 introduced a new way to measure line thickness (in points
>besides pixels) and the pen style thickness value of 0 is now
>forbidden. It was one way to say no line. Now you must use the
>pen pattern code of 01 for no line and a non-null value for
>thickness.
>
>You will have to go into your wor, identify the pen, or makepen
>statements and make sure they are like pen(1,1,black)
One of the items listed in the details of the MI Pro 5.0.1 product
description below is a correction for this very problem.
Specifically: Bug Fix #18 - No longer cause error when a Pen(0,0,0)
is found. Silently convert it to Pen(1,2,0) which is a single pixel
solid line.
Subject: MapInfo Professional 5.0.1 is now shipping
MapInfo Professional 5.0.1
contains numerous bug fixes (including everything in 5.0.0.18
and 5.0.0.19 patches)
contains a couple of special enhancements (Polk Demographics,
DB2 support, Live ODBC MBR searching)
has been slipstreamed into North American production as of
12/22/98 (All localized 5.x already built on 5.0.1)
is available for download as a free upgrade to MI Pro 5.x (5.0,
5.0.0.18, and 5.0.0.19) at http://testdrive.mapinfo.com/mipro
-----------------------------Details------------------------------
Polk Demographics Copyright Information
The Claritas Trendline Demographics that previously shipped with
MI Professional are no longer shipping with the product. MapInfo
5.0.1 includes the Polk data sets: Demographics by County;
Demographics by State; Demographics by 5 Digit Zip Code. All are
Copyright 1998, The Polk Company, All Rights Reserved.
The War Office False Origin (Irish) Ellipsoid
This is an addition to the table in "Appendix I: Defining Custom
Datums/Datum Conversion" in the MapInfo Professional User's Guide.
Number Ellipsoid a 1/f
49 War Office False Origin (Irish) 6377542.178 299.325
Universal Translator
double-byte enabled;
contains support for
the latest Shape file format;
updated AutoCAD metafiles and
updated Intergraph metafiles.
To produce successful results, the data you are converting must
be in the language of the system you are using.
DB2 Client/Driver
is certified for linked-access tables only.
for Windows 95, Windows 98 and Windows NT v5 Maintenance.
To get a copy:
Access: http://www.software.ibm.com/data/db2/db2tech/db2nt95v5.html
Select: IDB2 Family for Windows 95/98/NT Version 5 FixPaks
The MapInfo ODBC layer MBRSEARCH option
There is a new option for ODBC live access layers which
controls whether MapInfo will append an MBR search spatial
predicate to your table defining query during a map draw
from the layer.
This is called the MBRSEARCH option.
Now you can turn off the MBRSearch predicate that is customarily
appended to your query. This is useful for an ODBC table on IUS
which is defined using a spatial predicate and where the additional
MBR search spatial predicate forces a complex query which does not
efficiently use the IUS spatial datablade spatial index.
This is also useful for an ODBC table on Spatialware for Oracle
which is defined using a non spatial predicate on some attribute
column.
The MBR spatial predicate that is appended will be used first to
drive the query which is not always the most optimal query plan.
However if the non spatial predicate is more efficient, you can
turn the MBR search off and achieve better performance.
Try the MBRSEARCH flag on and then off and see which way provides
the best mapper draw performance for a table for your application.
The Register Table MBRSearch option
[MBRSEARCH {ON (default) / OFF}]
Example:
Register Table "tgleditsmall"
TYPE ODBC TABLE
"Select * From informix.tgleditsmall"
CONNECTION
"DSN=IUS-Adak;UID=informix;PWD=informix;DATABASE=sw;HOST=adak;
SERVER=adak_tli;SERVICE=sqlexec;PROTOCOL=onsoctcp;"
CACHE OFF
MBRSEARCH OFF
Into "C:\Programs\MapInfo\Professional\4.5\Data\tgleditsmall.TAB"
For an existing TAB file, you can add the mbrsearch option to
the ODBC Tab file metadata section as follows:
!table
!version 500
!charset WindowsLatin1
Definition Table
File "uscty_8k"
Type ODBC
begin_metadata
"\DATALINK" = ""
"\DATALINK\Query" = "select ""SW_MEMBER"", ""SW_GEOMETRY""
from ""GEORGETOWN"".""USCTY_8K"" WHERE ""SW_MEMBER""=538"
"\DATALINK\ConnectionString" =
"DSN=sw35-huron;HOST=199.29.2.243;UUID=oracle;UID=GEORGETOWN;
OSID=QADB1"
"\CACHE" = "OFF"
"\MBRSEARCH" = "OFF"
end_metadata
Other changes in 5.0.1
Merged ODBC enhancements from MapX 3.5.1
Bug Fix #1 - DeleteTargeDistrict: index to target and deleted
district was stale. Now, we rely on fetching the districts
by name and then getting the proper index before doing
anything with that index.
Bug Fix #2 - If you set your display settings on your machine
to Large Fonts, characters in the info tool won't be displayed
properly.
Bug Fix #3 - Read Only metadata tag is removed when saving
MapInfo tables from a CD to a hard drive.
Bug Fix #4 - Multiple MapperInfo() calls produce memory leak.
Bug Fix #5 - Support extended character sets in MI/Crystal.
Support extended charsets for column names. Set appropriate
typeface and character set information into the Crystal Reports
report file.
Bug Fix #6 - Excel 97 table will not open in MapInfo 5.0.
Bug Fix #7 - Fix GetPaletteFromFile() so that it will no longer
read more than 256 palette entries and crashes.
Bug Fix #8 - Browser for new table behaves oddly.
Bug Fix #9 - Modify a grid theme whose min and max values are the
same causes a Floating Point Exception then crash.
Bug Fix #10 - Change Edit menu to say Copy Legend Window instead
of just Copy so users know that selections in legend windows
are irrelevant (we copy the entire window).
Bug Fix #11 - Using a three-value thematic template with two ranges
crashes MapInfo.
Bug Fix #12 - Opening Excel 97 tables in MapInfo 5.0 truncates the
last character in character or general columns.
Bug Fix #13 - Alter MapInfoDialog statement does not change the
preferred view in the Open Table dialog.
Bug Fix #14 - In an integrated mapping application, MapInfo crashes
after the Info Tool has been used to examine records by clicking
in the map window.
Bug Fix #15 - If you remove the layer of the record being shown in
the Info Tool window, then use the >> button to view the record
for other layers in the list, you will crash MapInfo when you get
to the end of the list.
Bug Fix #16 - Can't use GetObject() from an Integrated Mapping App
with the Runtime version of MapInfo.
Bug Fix #17 - Don't notify legend windows that mapper closing until
after mapper has called ObjWinClose.
Bug Fix #18 - No longer cause error when a Pen(0,0,0) is found.
Silently convert it to Pen(1,2,0) which is a single pixel solid
line.
Bug Fix #19 - Don't allow SelectionInfo to work on private
selections (such as selections in cartographic legend windows).
Bug Fix #20 - ReadAndApplyLegendLabels: Make labels visible if they
are custom. ThmInitForPreview: pie and bar themes. Init and show
as many legend labels as we have theme variables.
Bug Fix #21 - Crash, when using Info Tool on reopened tables.
Bug Fix #22 - MapInfo crashes when you close a QueryN table based on
a QueryN-1 that was created via an SQL select statement.
Bug Fix #23 - Message "Unable to save workspace" when trying to save
to a Netware server from an NT40 machine running Novell's client.
Bug Fix #24 - "Select * From Table" in live ODBC access will crash
MI Pro.
Bug Fix #25 - Individual value shading doesn't create the shade
value correct then errors: Variable to field button not defined.
Bug Fix #26 - SPW/IUS 3.5 I create an index and MI Pro still thinks
its read only.
Added some control hot-keys and changed others so that they were
unique on surface thematic dialog.
Fix tab ordering for a few dialogs.
Fix multi-open of tables on Win NT from a DBCS directory name
Fix linking EasyLoader and MIMFAL.LIB
Fix so that the Help button will be able to display the help file.
Items included from MapInfo Professional patch v5.0.0.19:
A fix for the GeoReg utility that would not correctly open GeoTiff
files in MapInfo Professional. GeoReg is a MapBasic tool used to
read registration information from raster (TIFF) files and
automatically load the image using the correct place on the earth.
This eliminates the hassle of having to manual register the raster
image.
A fix for the truncation of the end character for a text field when
a Microsoft Excel 97 (*.xls) table is opened.
Items included from MapInfo Professional patch v5.0.0.18:
Fixes
A fix for an application error when you modify a grid theme whose
min and max values are the same. This caused a Floating Point
Exception.
A fix for an application error when you create a thematic map on
a selection.
A fix for an error when you choose Table->Maintenance->Delete
Table for a Live Remote ODBC Access table.
A fix for an error when you choose Table->Maintenance->RenameTable
for a Live Remote ODBC Access table and it did not rename the
tab file.
A fix for saving edits to an ODBC layer fails when there is an
open theme in the mapper. This previously caused an error.
Fix for the following: Live ODBC Access MapBasic FETCH command.
Fetch Rec n is the only valid Fetch syntax for Live Access
Tables. FETCH FIRST fetches record 1 and works correctly unless
the first row is delete because then it will try to FETCH NEXT
and encounter the problem described below. FETCH LAST sets the
record number to the number of rows and will work unless the
last row is deleted because then it will generate FETCH PREVIOUS
and hit the problem described below FETCH REC n works in all
cases. FETCH NEXT will always fail with "FUNCTION SEQUENCE
ERROR". This is because FETCH NEXT will try to do an ODBC FETCH
NEXT but there has been no command issued to Open a cursor for
us to FETCH on FETCH PREV causes an infinite loop.
Work-arounds
Remote tables that are accessed via Live Remote ODBC Access and
have character columns in which the field contains either a quote
(single or double) or apostrophe character will fail against
database systems that use these same characters as string
delimiters. Currently ODBC access (both Linked tables and Live
Remote ODBC Access) do not parse fields to check for these
characters prior to uploading changes and this can cause a general
syntax or string not matched error. The work-around is to remove
these characters from the string and the table will function
correctly.
Other
A new tool has been added to the /TOOLS directory. MISetMBR.MBX -
This addresses the problem of opening Live ODBC tables where the
MBR is sized incorrectly. This program will update the MapInfo Map
Catalog with an accurate MBR. To install, select Tools > Tool
Manager, click "Add Tool" and fill in the location box.
Patch Installation:
If you install MapInfo Help, Tools or MapBasic after you apply
the patch you will need to run the patch again to update the
files.
LMEF 3.1
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
