mapxtreme united states technical support …...• in visual studio 2015, while adding references...

Location IntelligenceGeographic Information Systems

UNITED STATESpitneybowes.com

Technical Support

support.pb.com

CANADApitneybowes.com

Technical Support

support.pb.com

EUROPE/UNITED KINGDOMpitneybowes.com/uk

Technical Support

pitneybowes.com/uk/support

ASIA PACIFIC/AUSTRALIApitneybowes.com/au

Technical Support

pitneybowes.com/au/support

© 2016 Pitney Bowes, Inc.

MapXtremeVersion 8.0

Release NotesThese Release Notes provide information on enhancements and updates made to MapXtreme 8.0. It also covers bug fixes, known issues, and other important information for this release.

This document is a supplement to the MapXtreme Developer Guide. Refer to this document for release specific information and to the Developer Guide for overall product information and usage. The Developer Guide is available from these locations:

• PDF version accessible from the Start > All Programs menu under MapInfo > MapXtreme 8.0 > Learning Resources browser

• PDF version on the Pitney Bowes website

http://support.pb.com/ekip/index?page=product_content&cat=SC_MAPINFO_MAPXTREME

MapXtreme 8.0 Release Notes

Contents:

1. MapXtreme Version 8.0 Release Notes 31.1 What’s New 31.2 MapInfo Professional Inter-Operability 51.3 What’s Changed 61.4 Bug Fixes 61.5 Known Issues 71.6 Installation Requirements 8

2. MapXtreme Version 7.3.0 Release Notes 102.1 What’s New 102.2 What’s Changed 122.3 Bug Fixes 132.4 Known Issues 142.5 Installation Requirements 202.6 Installation Guidance 222.7 Performance Recommendation 23

MapXtreme 8.0 2 Release Notes


MapXtreme Version 8.0 Release Notes

What’s New

New Tech Stack • Visual Studio 2015

OGC GeoPackage

GeoPackage is an open format for Geospatial Information defined by OGC (http://www.geopackage.org). It is a new SQLite-based extension defined by the OGC to promote portability of data across platforms and products.

A GeoPackage is a platform-independent SQLite database file that may contain:

• Vector geospatial features• Tile matrix sets of imagery and raster maps at various scales• Metadata

Since a GeoPackage is a database, it supports direct use, meaning that its data can be accessed and updated in a "native" storage format without intermediate format translations. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. This OGC® Encoding Standard defines the schema for a GeoPackage, including table definitions, integrity assertions, format limitations, and content constraints. The allowable content of a GeoPackage is entirely defined in this specification.

MapXtreme 8.0 now supports GeoPackage for Feature Tables only. You can perform the following operations in MapXtreme SDK for GeoPackage.

1. Open a table residing in a GeoPackage database.

2. Open a tab file pointing to a table residing in a GeoPackage database.

3. Cache the contents of multiple RDB server (Oracle, SQL) tables in a single GeoPackage database.

4. Create and Save GeoPackage files.

For more details refer to Developer Guide Chapter 19: Working with GeoPackage.



GeoPackage as a Cache storage-type for RDB server tables

MapXtreme has exposed GeoPackage database to be used as a Cache for RDB tables. The benefit of using the GeoPackage storage-type for caching RDB server tables is that contents of multiple tables are cached in a single GeoPackage database (.gpkg) file, thereby using fewer temporary files. This is important for caching large number of tables in environments with limited number of available file handles.

Multi Resolution Raster (MRR)

MRR is a new raster data format (64-bit only) that encompasses all types of raster data like image, classified, discrete, and continuous. Though there are already more than a hundred raster data formats, there exists a requirement for a new, unifying, format that handles all types of data and provides new capabilities to improve the user experience when visualizing and processing raster data.

The size and number of raster datasets available to the GIS professional is growing rapidly. The resolution and coverage of remote sensing platforms increases with every new generation of hardware. The physical number of satellites and other remote sensing platforms in operation is increasing year on year. Storing, managing, visualizing and processing this data is becoming increasingly challenging for data providers and consumers.

To meet these challenges, Pitney Bowes has developed a new raster storage format called ‘MRR’. It provides a flexible solution for the entire spectrum of industry requirements. It is a unifying and enabling technology. It unifies the storage of all kinds of raster data – imagery, spectral imagery, continuous gridded data and thematic data – and removes the barriers to working with different kinds of raster data in the same context. It enables the highest quality visualization and processing of raster data – at any scale and for a raster of any size.

The capabilities of the MRR format are listed below:

• Storage of image data, classified (thematic) data, continuous and discrete data.• Removes all restrictions on the size of raster datasets which means it supports raster

datasets of virtually unlimited size.• Extends the concept of a raster from a simple 2D array of cells to an extensible, sparse

matrix of tiles.• Contains a data pyramid that provides access to data at any scale in linear time.• Achieves efficient storage using lossless and lossy compression techniques via

industry standard compression codecs.• Supports the temporal dimension, allowing data to be accumulated and accessed by

time.



• Supports a wide number of data types including complex numbers.• Supports a wide and extensible number of data types including complex numbers.• Stores one or more multi-banded fields.• Provides local registration and cell size for each field, and tile decimation.• Computes and stores high quality statistics to support rendering.• For simplicity, an MRR is contained within a single file on disk.

For more details refer to Developer Guide Chapter 17: Working with Rasters and Grids.

Performance Improvement in RDB Query Execution

MapXtreme 8.0 comes with faster query processing for Oracle and SQL server tables. Operations such as inserting, updating and querying data execute faster in MapXtreme 8.0 as compared to version 7.3.

OGC certification

MapXtreme 8.0 for English is OGC certified for WFS 1.0.0, WMS 1.1.1 and 1.3.0.

MapInfo Professional Inter-Operability

NativeX (Extended TAB) file support

MapXtreme supports newly added Extended TAB (NativeX) file format by MapInfo Professional. This NativeX TAB file supports UTF-8 and UTF-16 charsets as well as it can store the data files that are greater than 2GB in size. MapXtreme user can also use NativeX as Cache storage type similar to Native for disk and memory based caching.

MapFile block size

MapXtreme user can change the Map file Block Size for enhanced performance of reading and writing Native and Native X Files. This can be achieved by specifying the block size at the time of table creation only.

Coordinate System changes

MapXtreme has incorporated latest co-ordinate system additions from MapInfo Professional. In addition to several new coordinate systems, EPSG codes for many existing coordinate systems have also been added.



A new codespace WKT has been introduced in MapXtreme 8.0 to identify coordinate reference systems through their OGC well-known text (WKT) representations. For more details regarding OGC WKT representation, visit http://www.opengeospatial.org/standards/wkt-crs.

MapXtreme 8.0 also supports Rectified Skewed Orthomorphic (RSO) projection method, which is used in coordinate systems of Malaysia and Borneo.

The following new datums have been added in this version.

• Japanese Geodetic Datum 2011 (JGD 2011)• Timbalai 1948, Everest 1968• GDM2000 datam, Malaysia• MAGNA-SIRGAS• Aratu• Barbados• Beduaram• Conakry 1905• Dealul Piscului 1930• Douala• Final Datum 1958• Makassar• Manoca

What’s Changed• In MapXtreme 8.0, the licensing requirements have been removed. Now the user does

not need to obtain any license (.lic) file to use the MapXtreme SDK.• With the removal of licensing requirement, we have discontinued the NCP and SCP

variants of MapXtreme Installer and replaced them with a single installer.• MapXtreme no more supports SpatialWare along with SQL Server 2000 and 2005.• Mapxtreme 8.0 does not support development on Visual Studio 2012 or its previous

versions.

Bug Fixes• Adornments and legends pushed out of the page boundaries while printing.



• Size of the legend border changes with the ExportSize when exporting a map to .bmp image.

• Attempt to update a table-cell with a string containing a ’?’ character within a set of double quotes (for eg, Some“data?”) results in an exception.

• Error in processing WMS Capabilities xml in which the tags are not strictly ordered as per the OGC WMS standard.

• MapXtreme should throw meaningful exception instead of StackOverflowException when attempting to open a Layer Control for a map containing an adornment.

• Incident Report M11339 - MapXtreme license file had to reside in two directories before Exponare recognises it.

• MapXtreme throws an exception while running an update query that involves a clip operation.

• Application stops responding when attempting to create grids on 64-bit Windows Server 2012.

• Raster Reprojection State Persistence Issue • MapXtreme WMS client sends duplicate requests

Known Issues• Bing Tile Map will not work as expected if .NET Framework 4.6 is installed on the

system. User application may hang or crash while working with Bing Tile Maps. As mentioned in Microsoft Security Bulletin MS15-092 (https://technet.microsoft.com/en-us/library/security/ms15-092.aspx), this is a known issue and you need to use the workaround provided by Microsoft.

• In Visual Studio 2015, while adding references of MapXtreme 8.0 assemblies to a new C# or VB project, the “CopyLocal” property of assemblies is True by default. It is advisable to set the same to False after adding the assemblies.

• The newly added 64-bit raster handler for MRR files, i.e., MIRasterHandler.rhz, can also open vertical mapper (.grd and .grc) files. However, since MIRasterHandler.rhz handler treats grid files as raster files, only raster related functions, such as MI_ImageFile, MI_ImagePixelWidth and MI_ImagePixelHeight, can be used. The grid related functions, such as MI_GridValueAtPixel, MI_GridMinValue and MI_GridMaxValue will not work on .grd and .grc files opened by the MIRasterHandler.rhz handler.

• Before installing itself, MapXtreme 8.0 installer will attempt to install Microsoft Visual C++ 2015 Redistributables if they are already not present in the system. This may fail on Windows 8.1, Windows 2012 R2 and Windows 10 due to other updates required by Visual Studio 2015. Please see Microsoft Knowledge Base articles KB2919355 and KB2887595 or contact Microsoft Support for the resolution.



• The Culture of all MapXtreme 8.0 applications is set to en-US (Locale ID = 1033) by default. To change this setting, you need to specify the locale ID corresponding to key “MapInfo.Engine.Session.LanguagePreference" in the application configuration. For example, to set the culture to en-GB, the following needs to be added to App.config file. <add key="MapInfo.Engine.Session.LanguagePreference" value="2057"/>

Go to the URL below to see the full list of Locale IDs.https://msdn.microsoft.com/enus/goglobal/bb964664.aspx.

Installation RequirementsPitney Bowes has tested and supports MapXtreme 8.0 on the following:

Operating Systems Windows 10 (x86, x64)Windows 8 and 8.1 (x86, x64)Windows 7 (x86, x64)Windows Server 2012 R2 (x64)Windows Server 2012 (x64)Windows Server 2008 R2 (x64) Windows Server 2008 with SP2 (x86, x64)

Architecture 64-bit32-bit

Development Framework and IDE Support *

Microsoft .NET Framework 4.5.2 Visual Studio 2015Visual Studio 2013

Browsers Internet Explorer 10 and above**

Firefox 3.5 and higherChrome 20 and higher

For web application and deployment: IIS 10 (Windows 10, Windows Server 2012 R2)IIS 8 and above (Windows 8 and 8.1)IIS 7 (Windows Server 2008R2, and Windows 7)


https://msdn.microsoft.com/enus/goglobal/bb964664.aspx

https://msdn.microsoft.com/enus/goglobal/bb964664.aspx


Minimum System Requirements

Supported databases Microsoft Access 2007 and Excel 2007Microsoft Access 2003Oracle 11G (11.1.0.6.0 and 11.1.0.7.0)Oracle 10G, 10GR2Microsoft SQL Server 2014 Microsoft SQL Server 2012 (with SQL Native Client 11)Microsoft SQL Server 2008 (with SQL Native Client 10)

For data access: MDAC 2.8

* Recommended development environments (IDE). Others can be used, however, the MapXtreme installer will not integrate its templates, samples, and help system.

** The MapXtreme Learning Resources displays in Internet Explorer automatically, regardless of your default browser setting. This will not change your default browser setting.

Memory Windows 7 and 8: 1 gigabyte (GB) RAM (32-bit), 2 GB RAM (64-bit)Windows 10: 1 gigabyte (GB) RAM (32-bit), 2 GB RAM (64-bit)Windows Server 2012 R2: 1 GB RAM Windows Server 2008: 512 megabytes (MB) RAM

Processor Windows 10: 1 GHz processorWindows 8, Windows 7: 1 GHz processorWindows Server 2008/2012: 1 GHz processor

Video Card Graphics card that supports at least 256 colors



MapXtreme Version 7.3.0 Release Notes

What’s NewMapXtreme includes the following new features in version 7.3.0.

Tile Server

MapXtreme supports the display of Tile Server TAB files created by MapInfo Professional. This allows you to open and view map tiles, such as Bing Maps and a Spatial Server MapTiling service from a MapXtreme desktop or web application.

Tiles are portions of maps that are stored on tile servers and on request, delivered as images to the client application for display. MapXtreme opens and displays tile images in the same way that it supports raster or WMS images. Images can be brought into MapXtreme as individual layers or as part of an .MWS workspace.

MapXtreme has built-in caching support for tiles for faster access of tile images. The cache is maintained during the session that the desktop or web application is open. You can also apply style overrides to Tile Server layers to control the translucency, brightness, contract and grayscale of the images, in the same way as you do for raster layers.

A Tile Server C# desktop sample application is available to help you gain more insight on how to use the tiling capability. It is located in \Samples\VisualStudio201x\Desktop\Features\TileServer under your MapXtreme 32-or 64-bit install directory.

For more information see Chapter 18: Working with Maps from Tile Server in the MapXtreme Developer Guide.

FDO Extension

A 64-bit FDO Provider Sample Extension has been added to the product.

SQL Database Table

Handling of fraction part of DECIMAL column has been added for various operations to enable more accurate floating point calculation used at server side logic.



MapXtreme Setup Project

Creation of a MapXtreme setup project can be enabled in Visual Studio 2013 by installing Visual Studio Installer Projects Extension. For more information see:

https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d

or

http://blogs.msdn.com/b/visualstudio/archive/2014/04/17/visual-studio-installer-projects-extension.aspx

For Visual Studio 2012 you will need to use a third party tool to create a MapXtreme setup project.

WMS and WFS Certification

MapXtreme v7.3.0 for Japanese and Chinese is OGC certified for WFS 1.0.0, WMS v1.1.1 and v1.3.0.

Ellipsoid and Datum Support

Ellipsoid• GCS (GCS_SPHERE)

Datum ID• SerbiaMGI1901 (Serbia datum MGI 1901)• NorthSaharaParameter7 (North Sahara 7-parameter)• HD72Updated (HD72 (Hungarian Datum of 1972) - Updated)• SJtskCzech (S-JSTK (Czech))• JTSK03Slovak (JTSK03 (Slovak Republic))

New System Support• Visual Studio 2013 Support• .Net Framework 4.5.2 support

MapXtreme Installer

The MapXtreme installer will add the following environment path variables with empty values:

• MI_TILE_SERVER_KEY: To set the Tile Server key for Bing Tile Server maps


https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d




• MI_MAX_FILE_HANDLES To set the maximum number of files MapXtreme can open, up to 2,040.

• MI_ECW_MAX_CACHE To change the default cache memory for ECW handler.

MapXtreme installer will also add following registry key with an empty value:

• SOFTWARE\MapInfo\MapXtreme\7.3.0\TileServerKey To set the Tile Server key for Bing Tile Server maps.

What’s ChangedMapXtreme v7.3.0 supports the .NET Framework 4.5.2. Applications created with an earlier version of MapXtreme (v7.1.0 or v7.2.0 with .Net Framework 4.0 support) will not run as expected. These applications can use the assemblies of MapXtreme v7.3.0 by making minimal changes through a configuration file to redirect the application to v7.3.0 assemblies. This will avoid the need to recompile desktop or web applications and allow your existing setup to work with MapXtreme v7.3.0. Instructions are contained in the following sections.

Redirection for Desktop Applications

To redirect existing MapXtreme v7.1.0 or v7.2.0 based desktop applications to use the v7.3.0 assemblies, modify the app.config file as shown in the illustration below. Do this for each assembly under the runtime section. The public key token value is the same for the old and new assemblies.



Redirection for Web Applications

To To redirect existing MapXtreme v7.1.0 or v7.2.0 based web applications to use the v7.3.0 assemblies, modify the web.config file as shown in the illustration below. Do this for each assembly under the runtime section. The public key token value is the same for the old and new assemblies.

Additionally, change all references from the old assemblies to the new assemblies in WebForm1.aspx.

MapXtreme Developer Guide

MapXtreme Developer Guide in CHM format is no longer provided. The same information is contained in the MapXtreme_DevelperGuide.PDF version which is located in the Documentation folder after installation.

Bug FixesThe following issues were resolved in this release.

• Labeling problems when based on DateTime/Time columns.• Cannot save or load custom legends to a workspace.



• Objects in MapFactory and LegendFactory are not cleared before deleting the miApp object.

• ArrowToolStripButton generates erroneous code in the designer.• CustomLegendFrames are not saved to workspace.• Drag and drop a workspace onto Workspace Manager results in unexpected layer re-

ordering.• Linear Referencing: LocateMeasure API is crashing when point lies outside the curve

and curve is closed.• Changing columns while creating range theme on a label layer in Workspace Manager

resulted in error.• Issue with adding a feature with a drawing tool, then cancelling the operation did not

release add operation from the tool.• Edit issues with TAB file located in Documents or Desktop.• Printing behavior for bar theme and pie theme legends, as well as scale bar and title

adornments, has been fixed.

Known Issues

IIS 8.0 with .Net Framework 4.5

MapXtreme v7.3.0 based web applications on Windows Server 2012 that use IIS 8.0 may freeze where there are multiple concurrent users, due to a Microsoft limitation. See Issue 6 under the following KB document at https://support.microsoft.com/en-gb/kb/2828842. The workaround for this problem is to apply the hotfix or upgrade to .Net Framework 4.5.2.

MapXtreme v7.3 Help Integration on Windows 2008 R2 and Windows 2012 R2

Due to security settings in Visual Studio’s embedded Internet Explorer browser, the integrated Developer Reference may display the help content in raw HTML on Windows Server.


https://support.microsoft.com/en-gb/kb/2828842


A workaround will necessitate changing a local computer policy. Follow the process below. This will require administrator rights. More information about this issue can be found at https://connect.microsoft.com/VisualStudio/feedback/details/764536/help-viewer-2-0-displays-raw-html-due-to-company-enforced-security-policy.

We also provide a standalone Developer Reference that you can refer in place of the integrated version if you do not or cannot change the security settings. MapXtreme_DeveloperReference.chm is located in the \Documentation\Help folder under the MapXtreme installation directory.

To change the local computer policy for Internet Explorer:

1. Open the Local Group Policy Editor (Start > Run > gpedit.msc).

2. Under Local Computer Policy navigate to Computer Configuration / Administrative Templates / Windows Components / Internet Explorer / Internet Control Panel / Security Page / Local Machine Zone. No changes are needed to other security zones.

3. Locate the correct setting: either Open files based on content, not file extension (Internet Explorer 8 and below) or Enable MIME Sniffing (Internet Explorer 9 and above).

4. Double-click the setting to open it, and change its value to Disabled.

5. Click Apply, then OK.

6. To re-integrate the Developer Reference, follow the instructions in MapXtreme Help Integration on page 19.

Disabling Enhanced Security for Internet Explorer

If the Developer Reference still does not display properly, you may also need to disable the Enhanced Security Configuration for Internet Explorer.

To disable Internet Explorer Enhanced Security Configuration:

1. Close all instances of Internet Explorer.

2. Click Start, point to Administrative Tools, and then click Server Manager.

3. If a User Account Control dialog box appears, click Continue.

4. Under Security Information group, click Configure IE ESC.

5. Under Administrators, click Off.


https://connect.microsoft.com/VisualStudio/feedback/details/764536/help-viewer-2-0-displays-raw-html-due-to-company-enforced-security-policy

https://connect.microsoft.com/VisualStudio/feedback/details/764536/help-viewer-2-0-displays-raw-html-due-to-company-enforced-security-policy


6. Under Users, click Off.

7. Click OK.

For more information see res://iesetup.dll/IESecHelp.htm#overview.

Tile Server TAB and Authentication

While working with Tile Server TAB files, authentication (user & password) is not working for MapXtreme-based web application.

MapXtreme Tools Integration on Windows Server 2008 R2 and Windows Server 2012 R2

MapXtreme Tools are integrated with Visual Studio 2012 and Visual Studio 2013. However on Windows Server 2008 R2 and Windows Server 2012 R2, the tools may be not integrated due to securities setting or version updates. In this cases MapXtreme tool can be integrated manually or follow this procedure:

After using Visual Studio 2012 or Visual Studio 2013 at least once, re-run the MapXtreme installation program for proper integration of MapXtreme tools and templates.

Infrastructure

64-bit Applications on Visual Studio 2012 and Visual Studio 2013 Development Server. Visual Studio 2012 and Visual Studio 2013 do not support running 64-bit web applications in Development Server. An incorrect format exception is returned when running trying to run 64 bit applications.

Merge Modules additional requirements: If you are creating your own installer with our merge modules (not available in the Trial versions), you must add the following prerequisites: .NET Framework 4.0 (not the client profile), MSXML 6.0 and Visual C++ 10.0 CRT (x86 and x64). x86 is needed for both x86 and x64 apps.

ACE Drivers for Microsoft Access on 64-bit: The MS Access Database Engine contains components that facilitate the transfer of data between MS Office applications and non-Office applications. MapXtreme does not provide this redistributable. See http://www.microsoft.com/en-us/download/details.aspx?id=13255 for usage, limitations. On 32-bit applications you can continue to use the Jet driver which may perform better in multi-thread mode.


res://iesetup.dll/IESecHelp.htm#overview

http://www.microsoft.com/en-us/download/details.aspx?id=13255


Running .NET Framework 2 application on 64-bit Windows: When using the grant set <trust level="Full" legacyCasModel="true" />, an error message “Loading this assembly would produce a different grant set from other instances” is presented when you run a .NET Framework 2.0-based application on a computer that is running a 64-bit version of Windows. See http://support.microsoft.com/kb/2282372.

.NET Framework 4 Client Profile: MapXtreme does not support the .NET Framework 4 Client Profile. For more information see http://msdn.microsoft.com/en-us/library/cc656912.aspx.

Data Access

Column Named ‘NOT’: There is a MapXtreme issue parsing SQL statements containing columns named 'NOT'.

Rasters and Grids

GRD and GRC Limitations: MapXtreme 64-bit cannot open .GRD and .GRC files without a .TAB file. If .TAB is present these files are opened as rasters only using the vmgrid.rhl. They will not be opened as grid files. This does not apply to 32-bit MapXtreme.

Raster images in Multi-thread Mode: An unhandled exception may occur when attempting to open an ECW raster image when MapXtreme is running on 30 or more threads.

Re-projecting palate-based images with 256 colors: When image re-projection of a raster is turned on, it displays in MapXtreme with a black border. The workaround for this issue is to convert the image to non-palette based or reduce the image colors to below 256.

Raster/Grid Handlers and Oracle: MapXtreme may be unable to load some raster and grid handlers when the Oracle client is installed. This can occur when running a 32-bit MapXtreme application, such as Workspace Manager on either a 32-bit or 64-bit operating system. To work around this issue, add C:\Program Files (x86)\Common Files\MapInfo\MapXtreme\7.x.x\RasterGridHandlers to the beginning of your system PATH variable.

Oracle

Oracle Arcs and Circles: When MapXtreme reads Oracle arcs or circles, they are converted to a polygon representing the arc or circle. The resolution (# of points) defaults to 40, up from 20 prior to this release. You can specify a different number of nodes in your app.config or web.config by adding the following:


http://support.microsoft.com/kb/2282372

http://msdn.microsoft.com/en-us/library/cc656912.aspx

http://msdn.microsoft.com/en-us/library/cc656912.aspx


<configuration> <appSettings> <add key="MapInfo.Data.ArcNodeResolution" value="1000"/> </appSettings> </configuration>

Note that using a high number can affect performance.

ASP.NET Master Pages

The MapControl must be wrapped in a relative positioned <div> tag:

<div id="mapDiv" style="position:relative;">

<cc1:MapControl ID="MapControl1" runat="server" Height="300" Width="300" MapAlias="map1" />

</div>

Thematic Mapping

ModifyRangedThemeSettings control: The ModifyRangedThemeSettings control loses the appropriate count assigned to each Custom range when the number of ranges is increased.

Custom Legends and Workspaces: MapXtreme's workspace persistence format does not support saving custom legends. Custom legends are saved through serialization, however, not to the workspace.

MI SQL Time Functions

Date and Time Functions: The MapInfo SQL functions DateTimeToString and StringToDateTime do not work correctly. The documentation for StringToTime() and TimeToString() functions is incorrect. The following information is correct:.

StringToTime

Creates a Time from a character string.

Syntax

StringToTime (str)

Arguments

str is a string representation of a time

StringToTime cannot perform conversions on DateTime strings. Use StringToDateTime.



TimeToString

Converts a time into a string.

Syntax

TimeToString ( time, fmt)

Arguments

time is a time.

fmt is a string identifying the format of time. Remarks

TimeToString does not work with DateTime values.

Samples on 64-bit installations

Samples are installed under both Program Files and Program Files (x86) folders.

MapXtreme Help Integration

The Developer Reference may not integrate into Visual Studio when installing MapXtreme for English, Japanese, or Chinese on an English operating system under the following conditions:

• Visual Studio has not been run at least once, or • Visual Studio Help Viewer is set to Launch from Browser.

To remedy this, set your Help Viewer preference to Launch in Help Viewer and then manually integrate the Developer Reference following the procedure below:

1. From the Help > Add and Remove Help menu in Visual Studio, choose Disk from the Installation Source.

2. Navigate to the Help\Documentation folder under your MapXtreme installation. Select HelpContentSetup.msha and click Open, then Next.

3. Under the Actions column for MapXtreme Developer Reference click Add, then click the Update button.

4. At the Security dialog, click Yes to proceed. 5. At the conclusion of the integration process, view the MapXtreme Developer

Reference in the Contents pane .

MapXtreme Developer Guide and MapInfo SQL Reference: These components of the MapXtreme documentation set are not integrated into Visual Studio. They are available from the Learning Resource browser under the Documentation section. To open Learning Resources, from the Start menu navigate to MapInfo > MapXtreme 7.3.0 > Learning Resources.



Installation RequirementsPitney Bowes has tested and supports MapXtreme v7.3.0 on the following.

Architecture • 64-bit• 32-bit

Operating Systems • Windows 8 and 8.1 (x64)• Windows 7 (x86, x64)• Windows Server 2012 and 2012 R2 (x64)• Windows Server 2008 R2 (x64) • Windows Server 2008 with SP2 (x86 , x64)

Development Framework and IDE Support *

• Microsoft .NET Framework 4.5.2 • Visual Studio 2013• Visual Studio 2012 Upgrade 4

Browsers • Internet Explorer 8.0 and higher**

• Firefox 3.5 and higher• Chrome 20 and higher

For web application and deployment:

• IIS 8 and above (Windows 8/8.1, Windows Server 2012 R2)

• IIS 7 (Windows Server 2008, and Windows 7)



MapXtreme does not support the Express Editions of Microsoft Visual Studio.

Minimum System Requirements

Supported databases • Microsoft Access 2007 and Excel 2007• Microsoft Access 2003• Oracle 11G (11.1.0.6.0 and 11.1.0.7.0)• Oracle 10G, 10GR2• Microsoft SQL Server 2012 (with SQL Native

Client 11)• Microsoft SQL Server 2008 (with SQL Native

Client 10)• MapInfo SpatialWare® 4.9 and 4.9.2 for

Microsoft SQL Server 2005• MapInfo SpatialWare® 4.9.2 for Microsoft SQL

Server 2008 32- and 64 bit editions

For data access: • MDAC 2.8

* Recommended development environments (IDE). Others can be used, however, the MapXtreme installer will not integrate its templates, samples, and help system.

** The MapXtreme Learning Resources displays in Internet Explorer automatically, regardless of your default browser setting. This will not change your default browser setting.

Memory Windows 7 and 8: 1 gigabyte (GB) RAM (32-bit), 2 GB RAM (64-bit)

Windows Server 2012 R2: 1 GB RAM

Windows Server 2008: 512 megabytes (MB) RAM

Processor Windows 8, Windows 7: 1 GHz processor

Windows Server 2008/2012: 1 GHz processor

Video Card Graphics card that supports at least 256 colors



Installation GuidanceImportant: This is a full product maintenance release. You must uninistall your existing installation of MapXtreme before installing this version.

Installer: We recommend using the x64 installers on x64 platforms; even if your application is x86. The x64 installers will install the features/components needed for x86 development and runtimes. Currently we do not support having two versions of our installations. For example if you have version 7.3.0 installed and want to use the x64 version, you have to uninstall the x86 version, followed by installing the x64 version.

Installer - Run As Administrator: When installing MapXtreme on Windows 7, Windows 2008 Server and Windows Server 2012 R2, be sure that you specifically choose Run As Administrator from the shortcut menu. You must also be an administrator on the installation target.

Run Visual Studio as Administrator: Be sure that you are running Visual Studio as administrator for full privileges in the development environment.

How to Register MapInfo.CoreEngine in COM+:

Installing MapXtreme (x64) creates two COM+ applications - x86 and x64. If both objects (via Component Services) are not present, run the following commands in the specified given:

C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\REGSVCS.EXE /u /quiet C:\WINDOWS\Microsoft.NET\assembly\GAC_64\MapInfo.CoreEngine\v4.0_7.3.0.140__93e298a0f6b95eb1\MapInfo.CoreEngine.dll

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\REGSVCS.EXE /u /quiet C:\WINDOWS\Microsoft.NET\assembly\GAC_32\MapInfo.CoreEngine\v4.0_7.3.0.140__93e298a0f6b95eb1\MapInfo.CoreEngine.dll

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\REGSVCS.EXE /quiet /noreconfig C:\WINDOWS\Microsoft.NET\assembly\GAC_32\MapInfo.CoreEngine\v4.0_7.3.0.140__93e298a0f6b95eb1\MapInfo.CoreEngine.dll

C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\REGSVCS.EXE /quiet /noreconfig C:\WINDOWS\Microsoft.NET\assembly\GAC_64\MapInfo.CoreEngine\v4.0_7.3.0.140__93e298a0f6b95eb1\MapInfo.CoreEngine.dll

MapXtreme Help Integration: If you have removed the MapXtreme Developer Reference from Visual Studio, set your Help Viewer to use local help and then manually integrate the Developer Reference following the procedure below for your version of Visual Studio:



Visual Studio 2012 and Visual Studio 2013

1. Choose Help > Add or Remove Content.

2. In the Manage Content tab, navigate to\Help\Documentation folder and choose HelpContentSetup.msha. The MapXtreme Developer Reference will display in the list.

3. Click Add, then the Update button to integrate it.

4. At the Security dialog, click Yes to proceed.

Performance RecommendationSQLServer 2008 key selects and MIDataReader performance: When creating an MIDataReader from a SQL command statement built on a key select, we recommend using the pseudo key column name MI_KEY in the MapXtreme select statements, regardless of the real column name.

MapXtreme interrogates the SQLServer2008 table schema to determine the key, based available information, such as:

PRIMARY KEY indexIDENTITY columnUNIQUE identifierMI_PRINX column name.

This evaluated key is interpreted as "MI_KEY"

Since MapXtreme's SQL key SELECT behavior is optimized for MI_KEY use, we recommend that you use MI_KEY in your MapXtreme select statements, regardless of the real column name.

For example, if the table is defined with a PrimaryKey column 'MI_PRINX', the MIDataReader command should nonetheless reference MI_KEY for key select statements, otherwise,MapXtreme's SELECT behavior doesn't make use of the evaluated key column, so it potentially skips around the key select optimization.

In this example scenario, where MI_PRINX is defined as the key column, the following select statement exhibits performance issues over a large data set:

SELECT * from linkar WHERE MI_PRINX in (22924,22925,22926,22927,22928)

Whereas the following statement utilizes the key select to advantage to get acceptable performance, using the MapXtreme pseudo key column name, MI_KEY:

SELECT * from linkar WHERE MI_KEY in ('22924','22925','22926','22927','22928')

Note, MI_KEY is evaluated as a string during the select statement parsing, so you need to enclose the values in ''' marks.
