More Information About ArcPad® 7.1.1
This document contains important, late-breaking information on the following topics:
On the PC, ArcPad 7.1.1 supports the following versions of Windows:
· Windows XP
· Windows 2000
· Windows Vista
On mobile devices, ArcPad 7.1.1 supports the following versions of Windows:
· Windows Mobile 2003
· Windows Mobile 2003 Second Edition
· Windows Mobile 5.0
· Windows Mobile 6.0
· Windows CE 4.2
· Windows CE 5.0
On Windows Mobile and Windows CE devices, ArcPad 7.1.1 supports the ARM-based CPU chips. These include CPU chips from the following manufacturers:
· Intel (StrongARM, XScale)
· Texas Instruments (OMAP)
When using Microsoft XP, Microsoft ActiveSync 4.2 or higher is required to synchronize your mobile device with your PC. When using Microsoft Vista, Windows Mobile Device Centre 6.1 or higher is required to synchronize your mobile device with your PC.
The ArcPad Data Manager Extension for ArcGIS® Desktop require ArcView®, ArcEditor™, or ArcInfo® 9.2 or higher.
Installation on the Desktop
It is recommended that you uninstall any previous version of ArcPad 7.0 /7.1 from your desktop PC and Windows Mobile computer before installing ArcPad 7.1.1, however, the installation program will check for this and prompt you to uninstall.
If you intend to use ArcPad on a mobile device such as a Microsoft® Windows Mobile device, or Windows® CE device, you must install Microsoft ActiveSync® version 4.2 or greater on your desktop system BEFORE installing ArcPad. The latest version of Microsoft ActiveSync and other related technical information and resources can be found at http://www.microsoft.com/windowsmobile/default.mspx. If you are using Window Vista, you must install Windows Mobile Device Center version 6.1 of greater. The latest version of this can be found at http://www.microsoft.com/windowsmobile/devicecenter.mspx.
If you are familiar with previous versions of ArcPad, you will notice that the installation has changed. The choice of installing NADCON and HARN tables or not, has been removed, as is the choice of a custom install. In modern software terms, ArcPad is a relatively small application, so we have assumed a complete install for all. The time difference between the different installs is negligible and therefore we have removed any ambiguity that may occur in selecting an install option. All items are installed to the desktop.
The ArcPad 7.1 program group now contains:
· ArcPad 7.1.1 for Windows
· Datum Configuration Tool
· ArcPad Deployment Manager
The Datum Configuration Tool and ArcPad Deployment Manager are unchanged from previous releases. Note that the Datum Configuration Tool tool requires the Microsoft.Net 2.0 framework to be installed on your machine. You can find the framework here.
The ArcPad Deployment Manager is where you find all the components available to install to your mobile device.
All Help files have been grouped together for easier access.
The new ArcPad Data Manager Extension for ArcGIS is also installed automatically with ArcPad 7.1.1, as is Microsoft SQL Server 2005 Compact Edition (for the desktop version of ArcPad). In the case of Windows Mobile devices, you will need to deploy SQLce to your device using the ArcPad Deployment Manager (see below).
Installation on a Mobile Device
On Windows Mobile and Windows CE, it is highly recommended that you uninstall any previous version of ArcPad and ArcPad fonts before installing ArcPad 7.1.1. Removal of ArcPad from your mobile device can be performed using the Add/Remove Programs option from the Tools menu in Microsoft ActiveSync or Windows Mobile Device Center while your mobile device is connected to your desktop system. Alternately, you can use the Remove Programs option from the Settings menu on your mobile device.
After the desktop install is complete, the new ArcPad Deployment Manager will automatically display. Use this tree to install components to your (synced) mobile device. Windows Mobile items previously found in the ArcPad 7.1 program group (located under Start>All Programs>ArcGIS) are now in the ArcPad Deployment Manager. These include:
· Install ArcPad for Windows Mobile
· Install ArcPad StreetMap for Windows Mobile
· Install ArcPad Today Plug-in for Windows Mobile
· Install Datum Transform/s for Windows Mobile
· Install Language Pack/s for Windows Mobile
· Install Samples/s on Windows Mobile
· Install SQLce for Windows Mobile
· Install VBScript Runtime Library for Windows Mobile
Your mobile device does not need to be connected to your desktop system during the initial installation of ArcPad. If this is the case, simply close the ArcPad Deployment Manager and the install will finalize. You may install any of the Windows Mobile components to your mobile device at any time after successfully installing ArcPad on your desktop. To install, connect your mobile device to your desktop PC using Microsoft ActiveSync, and on the PC choose the ArcPad Deployment Manager from the ArcPad 7.1 program group. Although you are able to select more than one component to install to your mobile device at once, the language packs require ArcPad to be installed first. When you select more than one component, ArcPad does commence installation first, however, as it is significantly larger than the other components, on some mobile devices, the installation can be quite slow, and is incomplete when secondary components start to install. It is recommended that ArcPad is installed to mobile devices completely, before attempting to install language packs.
For Windows Mobile devices, you will need to deploy SQLce to your device using the ArcPad Deployment Manager. If you do not have a device synced to your desktop, you will see that several options are listed the Install SQLce for Windows Mobile category in the Deployment Manager. You will need to select the correct operating system for your device. If you have a device synced to your desktop before you open the ArcPad Deployment Manager, your devices operating system will be recognized and only the correct SQLce option will be displayed.
ArcPad Data Manager for ArcGIS Desktop
ArcPad Data Manager is an extension for ArcGIS Desktop 9.2 that gets installed with ArcPad 7.1.1. It replaces the ArcPad Tools for ArcGIS that comes with ArcPad 7.0 and 7.0.1. ArcPad Data Manager includes ArcPad geoprocessing tools for ArcToolbox and a toolbar for ArcMap. The ArcPad Data Manager for ArcGIS Desktop requires ArcView, ArcEditor, or ArcInfo 9.2 or higher.
To use the ArcPad Data Manager toolbar in ArcMap:
· Ensure that the ArcPad Data Manger Extension is installed and enabled (go to Tools > Extensions > and confirm ‘ArcPad Data Manager’ is in the list of extensions and a tick is beside it)
· Ensure that the toolbar is selected for viewing (right mouse click in the toolbar area, and confirm a tick is beside ‘ArcPad Data Manager’ in the list of toolbars)
There are two ways to browse to the ArcPad Tools Toolbox ArcCatalog:
· Firstly, navigate to your installation of ArcPad and locate the Toolbox manually. In a standard installation you will find the toolbox in C:\Program Files\ArcGIS\Toolboxes\ArcPad Tools. You can use the ArcPad tools straight from here, or for regular use, drag them to your Toolbox “favorites” window.
· Secondly, scroll to the very bottom of the file browser, and you will see a “Toolbox” main branch. Expand this and the “System Toolboxes” branch, and then open the “ArcPad Tools” toolbox. As above, you can use the ArcPad tools straight from here, or drag them to your Toolbox “favorites” window.
When you install ArcPad 7.1.1 you will notice that the ArcPad 7 tools no longer appear on the “ArcPad” toolbar (in ArcMap), only the ArcPad 6 tools. The ArcPad 6 tools remain because they are installed with ArcGIS (rather than with ArcPad). The ArcPad 7 tools are still installed, but are no longer automatically registered with the toolbar. If you find that you do need the ArcPad 7 tools, you can manually add them using the customize toolbar dialog. For new projects, there should be no need to add these tools, the ArcPad Data Manager performs all actions that these tools do.
If you are installing ArcPad 7.1.1 to a machine with ArcGIS 9.1 – the ArcPad Data Manager extension will install but not work, and the ArcPad 7 tools will be installed and registered to the ArcPad toolbar in ArcMap.
A small number of users have found that although the Copy Out (in the ArcPad Data Manager) tools did indeed work as documented, the Check Out tools did not work. If you witness this problem, please install the Microsoft Visual C++ 2005 SP1 Redistributable Package, found here.
Installing the ArcPad Data Manager Extension when ArcPad is installed prior ArcGIS
ArcPad can be used independently of ArcGIS on a PC. In this case, all of the ArcPad Data Manager Extension files are still copied to the PC during the ArcPad installation. If ArcGIS is installed at a later date, these files can be moved to the ArcGIS folder and the extension enabled. The files that need to be copied are listed in the table below:
Copy from folder
C:\Program Files\ArcPad 7.1\Help\
C:\Program Files\ArcPad 7.1\Help\
C:\Program Files\ArcPad 7.1\Help\
C:\Program Files\ArcPad 7.1\Desktop Tools\
ArcPad 7.1.1 includes language packs for the following languages:
· Arabic (Egypt)
· Chinese (Hong Kong)
· Chinese (Simplified)
· Portuguese (Brazil)
All of the language packs included with ArcPad 7.1.1 are automatically installed on the desktop PC when installing ArcPad 7.1.1. However, language packs need to be individually and explicitly installed on Windows Mobile and Windows CE using the ArcPad Deployment Manager on the PC. Once a language pack has been installed on a device, it can be selected from the Locale page of the ArcPad Options dialog box.
In order to use a language pack with ArcPad, the locale and codeset must be supported on the device. The Locale page of the ArcPad Options only lists the locales which are supported on the device. Your device’s operating system does not necessarily need to be localized for a particular language in order to use the language in ArcPad, but the operating system does need to support the language and codepage. For example, you can install the Chinese fonts, or codepages, on an English Windows XP PC. Once you have done this, you can use the Chinese locale with ArcPad, even though the Windows XP operating system is still in English.
Please contact your local ESRI International Distributor for information on available locales for Windows Mobile and Windows CE devices in your region.
What's New in ArcPad 7.1.1
This service pack predominantly contains fixes to issues raised since the release of ArcPad 7.1.
Enhancements to ArcPad
· Method to create GUID’s in ArcPad via scripting added – the new CreateGuid method (of the system object) returns a string in the standard GUID string representation
· Satellite objects added – a new property called ‘Satellites’ has been added to the GPS object. Satellites will return a collection of “Satellite” objects. If the InView argument is True, the Satellites collection contains all Satellites communicating with ArcPad. If it is False (the default), the Satellites collection contains the Satellites used in the current position only.
· Streetmap Desktop Data Extractor – the streetmap desktop data extractor utility allows ArcPad StreetMap users to extract data from the Streetmap Premium Tele Atlas NA dataset which included in ArcPad 7.1. Users may save the extracted area of interest to desktop PC, and then transfer it to the mobile device operating ArcPad in the field.
Issues addressed from the ArcPad 7.1 release
This service pack addresses a number of issues raised from the previous releases. Below is a summary of the issues which have been addressed, along with their corresponding reference number.
· Conflicting subtypes at check out – Individual subtype tables are created now with the naming convention of ST_<layer/tablename>_<subtypename>. This means that when you have multiple feature classes using the same field names for the subtype, there will no longer be clashes. (CQ00309706)
· When subtypes are used coded value domain tables are identifiable – similar to when there is no subtype defined, coded value domain tables in the AXF are prefixed with CVD_ (CQ00309546)
· Domain names which contain a slash ("/") did not check out – Domains that contain a slash ("/") in the name are now successfully checked out to an AXF (CQ00309677)
· Incorrect Checkbox behaviour in custom forms - Shapefiles with True/False controls on them now behave as 2-state check box controls as they did in ArcPad 7.0 (CQ00309742)
· RecordSet::AddNew on AXF layer crashes ArcPad - Recordset::AddNew no longer crashes ArcPad (CQ00309843, CQ00308698)
· Recordset::FindNearestXY causes ArcPad to crash - Recordset::FindNearestXY now is forced to use the current spatial index state and no longer causes ArcPad to crash (CQ00308698)
· SQLce reserved words fail to check out- SQLce reserved words no longer fail to check out to an AXF (CQ00309814)
· Unclear Layer definition XML – The XML formatting of the layer definition in an AXF file has been improved (CQ00309497)
· Failed Check out of GUID and GlobalID - GUID and GlobalID attributes can now be correctly checked out of a geodatabase into an AXF. Please note there is a limitation in ArcGIS 9.2 in that GlobalID's cannot be written back into the geodatabase, however GUID’s can be successfully checked back in (CQ00309652, CQ00309704, CQ00309945)
· Unable to install Datum Configuration Tool – this tool now installs and operates correctly on non English PC’s (CQ00309474)
· DOS window appears when ADD LAYER – The DOS window no longer appears when you select Add Layer on CE .NET devices (CQ00309812)
· Incorrect selection is made with RecordSet::Find and advanced select - selection now returns only the features selected (CQ00309558)
· GPS Stops working in ArcPad when power is turned off - Whenever there is GPS is activity, a periodic signal is now sent to Windows Mobile to prevent the device powering down based on idleness. The GPS now continues to work. (CQ00309907)
· Application.ExecuteCommand("movepointtogps") does not apply averaging – now when you invoke this command, the averaging dialog is displayed, and averaged GPS reading is collected (CQ00309846)
· Multiband planar format TIFFs are drawn incorrectly - Planar format TIFF images are now supported by ArcPad (CQ00309907)
· Sample utility extension didn’t work – To improve performance in ArcPad 7.1 all extensions were set to delay load (ie: remain unloaded until forced to load within ArcPad by a users action). The Notify Watcher sample extension could not be triggered within ArcPad so would not load until the delayload=”false” attribute was manually added to the ExtensionsPrefs.apx. All utility extensions now have delayload="false" as their initial default, so this manual edit is no longer required (CQ00309964)
· Vectronix Vector 1500 GMD rangefinder negative inclination errors – the interpretation of negative inclinations has been corrected for this rangefinder device (CQ00307656)
· Auto increment in shapefiles not working in ArcPad 7.1 – auto incrementation defined in the form definition of a shapefile, has been repaired and now works. NB: this check box option is not active for AXF’s. (CQ00309747, CQ00309330)
· SiRF satellites are not shown in skyplot - On the Skyplot, the satellites used in obtaining in fix are now properly shown in black. Also, the Signal Strength graph now works (CQ00302207)
· Invisible fields in a feature class are partially checked out – In Arcpad 7.1, fields marked as invisible in ArcGIS where partially checked out – the field was created but no data was populated. Now, fields marked as invisible in ArcGIS are (correctly) NOT checked out at all (CQ00309933, CQ00309685)
· Multiple values for a symbol are not exported to the layer definition - when the same symbology is defined for multiple values, these now export correctly to ArcPad
· Symbology based upon more than one attribute field failed – symbology draw categories based upon "unique values, many fields" are now displayed correctly in ArcPad (CQ00293189, CQ00298746, CQ00138611, CQ00291312)
· Not all symbology for layer is exported – In ArcPad 7.1 and earlier, when multiple symbology headings are used, only the symbols from one heading were exported to the APL. Now all symbology is exported (CQ00164269)
· Unable to display features checked out to ArcPad when label field (in ArcMap) has nothing selected – when ‘label features in this layer’ is selected, and no label field is chosen, the first available field is now used as the default, and the features are correctly displayed in ArcPad (CQ00309979)
· Incorrect handling of EDIT control for numeric fields – In ArcPad 7.1 and earlier, if you used the 'backspace' key to clear the default value from a numeric field (in a custom form), the user would not be allowed to leave the page. This has been corrected, custom forms now behaving the same as the default feature properties dialog box (CQ00309556)
· AXF Draw Filters are not saved when created in ArcPad – Draw filters created in Arcpad are now saved (CQ00309968)
· Labels defined in ArcPad are not saved – Labels created in Arcpad are now saved (CQ00309968)
· ArcPad froze on error 80040E2F during editing - ArcPad no longer freezes when error displayed stating that attributes can not be saved because of non-compliance (eg: duplicate values in a identity field. CQ00309994)
· Find nearestXY falsely finds lines outside envelope – only lines within the search envelope are returned (CQ00310017)
· ArcPad Check Out crashes when incomplete date values (ie: time only) exist - Check Out no longer crashes when incomplete date values exist in the geodatabase. (CQ00309834). In these cases, ArcPad will include the earliest date that the database accepts.
· Using StreetMap make ArcPad slow – some performance improvements have been made for users of the StreetMap extension. Users should see a noticeable increase in available memory whilst StreetMap is running (CQ00309999)
What was New in ArcPad 7.1
Enhancements to ArcPad
The major feature introduced at ArcPad 7.1 is an out-of-the-box solution for supporting ‘related tables’. In previous versions of ArcPad, features in a Geodatabase were exported during the Check Out process and stored in shapefiles. Subtypes and domains were stored in the individual shapefile’s edit form. Relationship classes defined in the Geodatabase were not supported and user specific customizations got overwritten after each check out session.
In ArcPad 7.1 feature classes including relationships defined in the Geodatabase are extracted to a single ArcPad AXF File. Relationship rules including relationship classes as well as the subtypes and domains are maintained and enforced at the database level instead of forms (eliminating the overwrite which happens at the previous Check Out). Each feature can support multiple sets of attributes in separate tables. The user will be able to edit the features as well as the related tables in the field.
A new feature is the QuickProject. A new QuickProject will create a project folder named QuickProject_YYYYMMDD_HHMM and an apm called QuickProject.apm (which is automatically opened on creation). Three layers are created in the project: point.shp, polyline.shp and polygon.shp. Each of these layers have default QuickForm and contain the fields: Name, Category, Date, Comments, Photo. The Category field automatically contains a list of five categories (1-5) with the default of ‘1’, and a legend is created based on this field.
The QuickProject also demonstrates another new feature – the ability to modify the legend in ArcPad. Modifying the legend gives you the ability to ‘add codes in the field’. You are not actually modifying the underlying table, only the map legend. To do this, you use the (+) and (X) buttons appearing on the Symbology tab. These let you add or delete categories to the legend. You click on the legend entry itself to change the value and/or the legend, and is similar with the UI for related tables, but instead of adding to a table you’re just adding to a legend.
Also new are the Query Builder and Query Form. The ‘Criteria’ page on the Find dialog has been replaced with the ‘Query’ page. Here you can search up to three different fields. You also have the choice of ‘and’ / ‘or’ searches. The Results page has also been enhanced to include distance and direction (from centre of map or GPS location) to each returned feature and can be sorted. With ArcPad Application Builder you are able to create custom Query Forms. You can create one or many query forms for each layer, each providing different search criteria. Each form appears as a separate tab on the Find dialog.
The new Riverside sample data includes examples of the new features in ArcPad. It includes:
· Query and edit forms (single and multi page)
· Multiple feature layers for a single feature table - Streets and Streets (major). Streets (major) uses a filter of Category = 1 to only include major streets when zoomed out beyond 1:15000
· The Poles layers uses a filter of MAPSCALE less than 1:10000
· Singular and plural name definitions for related records (eg: 1 ‘light’, many ‘lights’)
· coded value domains that are dependent upon subtype fields and default values
· layer icons
ArcPad Data Manager
The ArcPad Data Manager extension for ArcGIS Desktop 9.2 that comes with ArcPad 7.1 includes Get Data For ArcPad and Get Data From ArcPad tools for both ArcToolbox and ArcMap. The ArcPad Data Manager allows the user to get data from the office to the field, deploy to multiple devices, and then update the Geodatabase with the field edits. The ArcPad Geoprocessing tools for ArcToolbox enable power users to automate repeatable Get Data for/from ArcPad sessions for batch geoprocessing.
ArcMaps Get Data for ArcPad tool also provides the added ability to specify a custom form at check out. The user can select an existing APL (or AXF) which contains customization to be applied on checked out layers.
The StreetMap Extension (previously sold separately) has been upgraded and is now included with ArcPad 7.1.1. Sample data for Rhode Island is included in the ArcPad install. A DVD with StreetMap Premium Tele Atlas North America (USA & Canada) data will be supplied with the released product. Other regions are also planned for future release.
StreetMap for the desktop installation is completed when ArcPad is installed. No further configuration is required. StreetMap can also be installed to a Windows Mobile device. Please note that the current release of StreetMap does not install to Windows CE.NET devices. We are working with device manufactures to fix this problem. To install StreetMap to your Windows Mobile device, you use the ArcPad Deployment Manager. You will need to install two items, the extension, and also the geocoding file for your region. These are listed under the Install ArcPad StreetMap for Windows Mobile category in the ArcPad Deployment Manager.
Issues addressed from the previous (7.0.1) release
ArcPad 7.1 addressed a number of issues raised from the previous releases. Below is a summary of the issues which were addressed, along with their corresponding reference number.
· Copying of Rasters - The Data Manager gives you three choices for copying out rasters: jpeg2000, tiff or ‘keep original’. The ‘keep original’ option eliminates issues with raster conversion experienced in the past (CQ00178432, CQ00165770, CQ00225105, CQ00292472, CQ00244790).
· Map naming – On the Get data for ArcPad wizard, you now have the option to select your own name for the apm file (previously automatically named ArcPad.apm. CQ00283047)
· Layer level snapping – you can now set snapping for individual layers. You can also select to view the snapping ‘buffers’ permanently for individual layers. This overcomes the problem on mobile devices that do not have a ‘centre’ button (CQ00297303, CQ00278005)
· NADCON and HARN ‘Do not install’ – now when you select ‘Do not install..’ these are not installed (CQ00299440)
· Screen Refresh – Screen refresh issues on the Allegro CE.net device have been corrected (CQ00280015)
· Proj.dll ‘not found’ warning – A message has been added to startup to warn if PrjData.dll is not found. The message includes the full pathname of the file so it is clear where ArcPad is attempting to load from. A missing PrjData.dll is the major cause for the GPS Datum’s combo-box to appear blank. (CQ00300492)
· Read Only layers – layers can now be set to read only. This is set during the ‘Get data for ArcPad’ wizard or in ArcPad Application Builder (CQ00297647)
· Deactivating USB GPS - Deactivating a USB GPS no longer causes a fatal error. NB: in this release ArcPad does not support USB GPS directly, only via third party software (CQ00278003)
· ArcPad toolbar always appear in ArcMap – This has been solved with the introduction of the ArcPad Data Manager. This toolbar honors the settings of: on, off, floating or docked when ArcMap is closed and restarted. The remaining ArcPad toolbar (which contains the ArcPad 6 tools installed with ArcGIS) will now also honor the same settings when ArcMap is closed and restarted. (CQ00284956)
· Editing non-versioned Geodatabases – Check out non-versioned data that is stored in an ArcSDE (both personal and enterprise) geodatabase is now supported in ArcPad Data Manager Extension. (CQ00297534)
· Cannot attach large image to a point feature in ArcPad – This has been solved in ArcPad 7.1 by using thumbnails to browse and display JPEG images. (CQ00303255)
The ArcPad 7.1.1 setup.exe includes PDF files of all the ArcPad documentation. The documentation is installed into the Help subfolder under the ArcPad 7.1 installation folder. This documentation includes:
· Installing ArcPad 7.1.1 (ArcPad_InstallGuide.pdf)
· Using ArcPad (ArcPad_UserGuide.pdf)
· ArcPad Reference Guide (ArcPad_RefGuide.pdf)
· ArcPad Quick Reference (ArcPad_QuickRef.pdf)
All documentation is available in Portable Document Format (PDF) and requires Acrobat Reader for viewing. You can obtain Acrobat Reader from Adobe's home page at http://www.adobe.com/.
Also included in the Help subfolder under the ArcPad 7.1 installation folder is the ArcPad Data Manager Extension help.
· ArcPad Data Manger Desktop Help (ArcPadDataManager_Desktop.chm)
· ArcPad Data Manger Developer Help (ArcPadDataManager_Developer.chm)
These are both compiled html files, no further software is required to open these.
Known Issues in ArcPad 7.1.1
The following are known issues with the ArcPad 7.1.1 release:
· ArcPad does not support ‘grouped’ values for symbology that can be created in ArcMap. Only the first value in the group list will be displayed in ArcPad.
Workaround: create a single field in ArcMap which combines the fields you wish to symbolise on, and use this field for defining symbology in ArcPad
Large toolbar buttons do not display
correctly on Windows CE 4.20.
Workaround: do not use large toolbar buttons.
Some label font sizes are not applied.
The cause of this issue is that not all fonts support all font sizes. Only
sizes which are supported by the selected font are applied.
Workaround: Select a different font size.
Taking a photo with the camera tool on a
Windows Mobile device may result in an error. The cause of the error is most
likely due to insufficient free memory to store the photo image file. As a
result, the camera module in ArcPad on the HP iPAQ hw6515 only supports resolutions of 640 x 480; 320 x
240 and 160 x 120.
Workaround: Reduce the resolution for the output image file in the camera tool settings.
module (on the PC version of ArcPad) is currently
limited to supporting cameras that support RGB compression. This is the case
for most modern cameras, but not older cameras such as the IBM UltraPort camera. The IBM UltraPort
camera uses YUV compression, and not RGB compression.
Workaround: Use the camera independently of ArcPad, and use the Pictures page, of the Feature Properties dialog box, to associate the photo image file with the feature.
· ArcPad allows the addition of multiple records to the related table of a one to one relationship (as defined in ArcGIS).
Workaround: A SQL command can be applied in ArcPad Studio, to set the Foreign Key to also be a Unique Key. This will mean that although the ArcPad user interface will appear to allow multiple records, the database will not allow an entry to be saved.
· Range domains are not enforced in related tables.
Workaround: Define the domain as a coded value domain.
· Captions do not display below Separator element when used in Toolbar submenu
Workaround: Do not use separator element in submenus
· If the max integer (2147483648) is entered into a long integer field (32 bit) in and AXF, the number is automatically clocked back to -2147483648. If numbers smaller than the minimum integer are entered (-2147483649), these numbers are accepted and do not change. Similar occurs for short integers.
Workaround: Define a range domain of -2147483648 to 2147483647 for long integers and -32768 to 32767 for short integers.
· In the feature properties dialog, data cannot be entered into an edit-box which has been changed from a combo-box based upon the selection made in another field. This feature properties dialog change, is the result of changing the subtype field elsewhere on the feature properties dialog.
Workaround: If a subtype is defined for a feature class, and one of the attribute fields of that feature class has a domain defined; domains must be defined for that field for EACH of the subtype values.
· Selecting the ‘parent’ checkbox in the ArcPad Deployment Manager for any of the options, does not select all of the child components. Each component selected will also have its own set of active sync message boxes which require user interaction to complete.
Workaround: Each component will need to be checked manually. There is no workaround for the multiple message boxes.
Design Decisions for the ArcPad 7.1.1 Release
The scope for supporting related tables out-of-the-box, is endless. We have consciously decided to implement specific features, which we believe, answer the majority of issues that users have raised throughout ArcPad’s lifetime. Keeping this in mind, the following is a list of design decisions that have been made for the ArcPad 7.1.1 release. In some cases, these features may be implemented in future releases of ArcPad.
· Feature class to feature class relationships not supported in the ArcPad UI – ArcPad 7.1.1 will support feature class to table, table to feature class, and table to table, relationships. We believe that these answer the bulk of relationship needs for the field user.
· User cannot create custom forms for related tables – custom forms can only be created for feature layers. Related tables appear as additional tabs (similarly to the picture and geography tabs) to the feature properties dialog. However, please note that the default feature properties dialog for both the feature class and the related table is significantly enhanced since ArcPad 7.0. The default dialog automatically displays combo-boxes, date pickers and check boxes where the geodatabase defines these particular field types.
· Filters only apply to drawing – A filter can be applied to feature layer to limit the features that are drawn on the screen. This has been introduced to provide a way to improve the drawing speed when large datasets are used. The filter does not apply to editing of features. New features can be added to layers that have a filter applied. If a scale filter is used, and the user zooms to a scale where features display, the newly created feature will display. The user can also ‘select’ features that have been filtered from display, either by clicking on the map, or using the Find tool.
· Invalid features are omitted from check out for features with subtype and coded value domain – If you have a feature class which has a subtype defined, AND you have a coded value domain assigned to one or more of the subtypes, AND you have some ‘invalid’ values in the field which is constrained by the coded value domain (eg: you may have imported the data from some other file type), the features with the invalid data will be omitted from the check out. These omitted features are listed in the check out log (xml file) that is created at check out. The behavior is slightly different in the case where no subtype is defined. If you have a feature class which does NOT have a subtype defined, however you do have a coded value domain assigned to a field, AND you have some ‘invalid’ values in that field (the one constrained by a coded value domain), these invalid values ARE checked out to the AXF file. The features can be queried and edited in ArcPad, but the field that is constrained by the coded value domain, can only have its value changed to a valid value. For example, a user obtains a feature class that contains historical data about the condition of sign posts. In the past, field workers were allowed to enter any descriptive text about the condition of the sign. Now you wish to ‘standardize’ the language used to assist in report generation. You create a coded value domain to constrain the way a field work can describe the sign (say there are now only two options: ‘satisfactory’ and ‘requires repair’). Then you check out the data to an AXF for the field worker to use. When the field worker inspects a sign that previously may have been recorded as ‘poor’, they are able to now use the drop down list to choose ‘satisfactory’ or ‘requires repair’. When the data is returned, this modification (which is now valid data) will be checked in successfully to the geodatabase.
MrSID, MrSID Decompressor, and the MrSID logo are trademarks of LizardTech, Inc., used with permission. Portions of this computer program are copyright © 1995-2004 LizardTech, Inc. All rights reserved. MrSID is protected by U.S. Patent No. 5,710,835. Foreign Patents Pending.