mapx50_sn - MapInfo MapX v5.0 Support Notes November 2002...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: MapInfo MapX v5.0 Support Notes November 2002 MapInfo Corporation Troy, NY Introduction The following items are currently unresolved issues and common misunderstandings in MapInfo MapX 5.0. If there is a known workaround, it is listed after the issue. The five-digit number that precedes each listing is that incident's bug number. If you need to contact MapInfo Technical Support regarding any of these issues, provide the MapX Support Spet with the bug number. Before installing MapX 5.0, you should completely uninstall any previous version (beta, trial version) from your desktop, then reboot. Current Bugs and Workarounds 15654 StreetWorks 3.0 tables cannot be opened with MapX 4.x or MapX 5.x. Workaround Use Streetworks 5.0 or change the paths in seamless layer’s component tables to include the full (rather than relative) path. 17420 Seamless layers do not display when the seamless table’s and component table’s coordinate systems have different bounds. Workaround MapInfo Professional has a tool “Check and Set CoordSys Bounds.” With this tool, you can set the coordinate system bounds of the seamless table to match the bounds of the underlying component tables. You will then have to click the “Save Table As...with Coordsys Bounds” button and save the seamless table to a different name. 19003 Calls to Layer.BeginAccess fail on SpatialWare for SQL Server layers. The same call does not fail for other SpatialWare layers (IUS, Oracle). Workaround Do not use Layer.BeginAccess or EndAccess with remote layers – the performance advantage provided by these methods is limited to native layers. 19040 Feature.Update does not always work for SpatialWare 4.5 for IUS. Workaround A change was made to MapX to use the last record in the subsequent select statement rather than the first. This results in better behavior, but is never a guarantee. The bug was changed to system limitation. You can handle this problem two ways: Option #1 First, you can specify some data value(s) during the initial AddFeature statement (line 5). The data specified only needs to uniquely identify the new feature from the original feature (e.g. it doesn’t need to be unique throughout the entire table). Of course, if it is possible that there are other records with features at that same location, then the data value(s) specified when adding the new feature must uniquely identify the new record from all of the overlapping records. A possibility would be to use a dummy value for Capital (since the code changes its value anyway). Consider the following code: For Each fCurrent In ftrs MsgBox i fCurrent.KeyValue = i sName = fCurrent.Name Dim newrvs As RowValues Set newrvs = ds.RowValues(fCurrent).Clone newrvs.Remove "province_name" newrvs.Remove "pop_1991" newrvs.Remove "sw_member" newrvs.Item("Capital").Value = "XXUNIQUEXX" Set ftr = newLyr.AddFeature(fCurrent, newrvs) ds.Refresh Set rvSet = ds.RowValues(ftr) rvSet.Item("capital").Value = sName ftr.Update False, rvSet ds.Refreshds....
View Full Document

This note was uploaded on 09/15/2011 for the course CSE mel2800 taught by Professor Horton during the Spring '10 term at Universidad del Turabo.

Page1 / 12

mapx50_sn - MapInfo MapX v5.0 Support Notes November 2002...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online