ArcPad® Application Builder 7.1.1 ReadMe

More Information About ArcPad® Application Builder 7.1.1

This document contains important, late-breaking information on the following topics:

· System Requirements

· Installation

· What's New in ArcPad Application Builder 7.1.1

· What was New in ArcPad Application Builder 7.1

· Known Issues in ArcPad Application Builder 7.1.1

System Requirements

On the PC, ArcPad 7.1.1 supports the following versions of Windows:

· Windows XP

· Windows 2000

· Windows Vista

Installation

ArcPad Studio 7.1 requires the following:

· Microsoft® XML Parser (MSXML 4.0 Service Pack 2 (SP2))

This parser can be obtained from Microsoft's Download Center MSXML 4.0 Service Pack 2. This should be installed on your desktop PC before starting ArcPad Studio.

· Microsoft ActiveSync® version 4.2 (for XP) or Windows Mobile Device Center version 6.1 (for Vista) must be installed before attempting to install ArcPad Studio. The latest version of Microsoft ActiveSync and other related technical information and resources can be found at http://www.microsoft.com/windowsmobile/default.mspx. For Windows Vista users, the latest version of Windows Mobile Device centre can be found at http://www.microsoft.com/windowsmobile/devicecenter.mspx.

The ArcPad Application Builder 7 program group on the PC is located under Start >All Programs >ArcGIS >ArcPad Application Builder 7.1.

Previous Installations

It is recommended that you uninstall any previous version of ArcPad Application Builder 7.0 from your desktop PC before installing ArcPad Application Builder 7.1.1. However, the installation program will check for this and prompt you to uninstall if necessary. Earlier versions of ArcPad Application Builder (ie: version 6) can remain on your PC when you install 7.1, as it will be installed to a new folder.

What’s New in ArcPad Application Builder 7.1.1

Issues addressed from the previous (7.1) release

· Missing Quick Start tutorial – the Quick Start tutorial has returned. The original tutorial remains, and two new scenarios have been include to demonstrate the use of AXF files (CQ00309837)

· Object Model Diagram (OMD) Updated – the OMD includes new objects Satellite and Satellites, and new method (to the system object), CreateGUID (CQ00309997, CQ00309977)

· Auto incrementation was broken for shapefiles – custom forms that have auto incrementation enabled will now work as in previous (to 7.1) versions of ArcPad (CQ00309330)

· Auto incrementation should be disabled for AXF layers – the auto incrementation check box on the Values tab of the EditForm properties dialog is not an option for AXF files, and is now ‘greyed out’ (CQ00309330)

· Manually entered elements not enforced in ArcPad – when a user manually creates elements in studio – they must be capitalised for arcpad to recognise them. Capitalisation is now enforced (CQ00309967)

· all values in the APX column (of AXF_LAYERS) in an AXF appear blank - < and > characters are now displayed in Studio, the result is that you can now see the layer definition XML in the APX column of the AXF_LAYERS table (CQ00309981)

· Semicolons inside strings (in an AXF layer) are treated as end of command – Semicolons are now treated as a normal character when it is inside a string (CQ00309982)

· Map.PointerXY and Map.PointerDisplayXY errors in Studio Help – these errors have been corrected, and now match the Object Model diagram (CQ00309972)

· Document ExtensionPrefs.apx – the following explanation of ExtensionPrefs.apx has been added to the Studio Help. The ExtensionPrefs.apx contains a list of extensions recognized by ArcPad and their delayed loading status. The first time you run ArcPad, ExtensionPrefs.apx will not exist, so every extension present will be loaded and examined. On subsequent restarts of ArcPad, ExtensionPrefs.apx is examined and only required extensions are loaded, saving time and memory (CQ00309969)

What was new in ArcPad Application Builder 7.1

Enhancements to ArcPad Application Builder

· AXF browser – In order to navigate AXF files created with the ArcPad Data Manager (to create and add custom edit and identify forms) a browser has been introduced to ArcPad Studio.

· Field picker – when editing a form, in addition to a control ‘picker’ a field ‘picker’ is also displayed. Use this to drag and drop attributes from your feature layer onto the form. When you drop the field onto the form, it will automatically choose the correct control type for that field. For example, if the field was defined in the original geodatabase as a date field, a date control will be added to the ArcPad form.

· Query Forms – Similarly to Edit and Identify forms, you can design Query forms for your feature layers.

· Domaincombo control – this new control dynamically changes depending on definitions in the source geodatabase. In ArcGIS you are able to define a combination of conditions for a field based on subtypes and domains. There are cases where this control will change from being a drop down box (where it represents a coded value domain), to an edit box (where it represents a range domain).

· Start/Stop editing button – This tool can now be placed on custom toolbars. The tool appears in the command list of the Toolbar dialog as the ‘toggleedit’ command.

· Read only layers – On the Layer Definitions Properties dialog (double click on the layer tag in the APL or AXF browser) there is now a readonly checkbox. Checking this box, forces the layer to be readonly in ArcPad. If checked, no checkbox is then displayed in ArcPad’s table of contents to make the layer editable.

Issues addressed from the previous (7.0.1) release

· Large tool buttons and drop downs - When large tool buttons used, drop downs also are enlarged (CQ00299950)

Known Issues in ArcPad Application Builder 7.1.1

The following are known issues with the ArcPad Application Builder 7.1.1 release:

· AUX objects' ReadLine property - The AUX objects' ReadLine property if set to True locks up ArcPad. There are alternatives to using the Rangefinder object or use AUX.ReadLine(False).

· Trouble hiding the Main toolbar - On some Windows CE devices you may encounter problems when hiding the Main toolbar in a default configuration file (ArcPad.apx). This is typically done when you want to replace the built-in toolbars with one or more custom toolbars. For example, if you have the following in ArcPad.apx, none of the toolbars may be created correctly:

If you encounter this problem, the work-around is to not create any of the built-in toolbars. You can do this by adding the 'create' attribute to the TOOLBAR elements and setting its value to false. You must do this for all three built-in toolbars. So your ArcPad.apx file would contain the following:

You would also have one or more custom toolbars defined that would replace the built-in toolbars. The 'visible' attribute of these custom toolbars would be set to true. For example:

· Files drag and dropped into Studio get imported into File Store of active AXF file - If an AXF file is the active window in Studio and then you drag ANY other file (APL, another AXF, VBS, .txt, etc.) into the Studio window - it gets imported into the File Store of the active window AXF file, rather than opened as another child window. A simple work around is to make a non AXF window active and then drag files into Studio, which will open if supported.

· Auto increment check box is incorrectly enabled for numeric bound fields in AXF files – Although enabled, you cannot use the Auto increment check box when working with AXF files. This option is only available with shapefiles. To implement auto increment functionality the user should design their geodatabase to utilize the OBJECTID field in these cases.

· The 'list values' tab is incorrectly displayed when a combobox is added to a form for an AXF layer – the ‘list values’ tab of the combobox control properties dialog is only applicable for shapefiles. It cannot be used to define lookup information for an AXF layer. To create a lookup up field in an AXF layer, ensure that a subtype or domain is defined in the source geodatabase, and use the ‘field picker’ to place the field on your custom form. Using the 'field picker' is the recommended way to build custom forms in ArcPad 7.1.1.