Unable to successfully check out data for ArcPad after 7.1 to 10 upgrade

[MatthewCarey]

I'm not sure if my problem is a 'devil in the details' one or something more fundamental, so any pointers appreciated.

We were happily working using ArcMap 9.3.1 to check out data with the ArcPad Data Manager extension v7.1 from a 9.2 geodatabase to a Nomad running Windows Mobile 6 and ArcPad 7.1.

We now have ArcPad 10 and ArcMap 10 (on development equipment, so we haven't ditched the older stuff).

Here's what I CAN do:
-Use ArcMap 9.3.1 to check out data with the ArcPad Data Manager extension v7.1 to check out data from the 9.2 geodatabase (we use a 7.1-generated .axf as a template with a custom form that uses some vb script)
- Manipulate/update that checked out data in ArcPad 10; the form works fine.
- Check it back into the geodatabase


Here's what doesn't work for me:
- Using ArcMap 10 and the ArcPad Data Manager extension v10 to check out data from the 9.2 geodatabase (or from a copy of it which is upgraded to 10) either using the same 7.1 - generated .axf as a template or with no template
- When checking out the existing features from the geodatabase, it fails at the validation stage and gives an error that for a certain field "value 0 is not member of coded value domain Yes_No."
- If checking out just the schema but still using the 7.1 - generated .axf, a successful checkout is apparently done, but when creating a new point using ArcPad 10, an error is thrown up about a Script Error that references MS SQL Server and states "the specified table does not exist" and "the source text is unavailable" (I suspect this is to do with the related tables that are part of the geodatabase).

This DOES work:
- If I use ArcMap 10 and the ArcPad Data Manager extension v10 to check out data from a 10 geodatabase, just the schema and not using a template (having it auto-generate the form), it does work.
- I can manipulate/update the data in ArcPad 10 (with a very basic form) and check it back into the geodatabase



In case it's not obvious, my final goal is to be able to check in and out data all within the realm of ArcGIS 10, using the custom form that's already been coded. It's not the end of the world to not be able to bring older data back into ArcPad, but it is necessary to use a heavily-customized form in order to make it user-friendly for our people working in the field.

It'd be great to get some insight on whether this might be a problem with a simple root cause, or whether it's something more complicated that will require modifications to the existing geodatabase and/or form.

Thanks, and apologies if some of my terminology is a little off, I haven't spent a lot of time working on complex ArcPad issues (OK, I'll confess that a consultant coded the 7.1 custom form but I do have some programming experience).

[TimHopper · Accepted solution]

Matthew,

Two main issues I see here:

1. You get validation errors when checking out existing data for disconnected editing.

2. When adding a new point, having utilized your custom form during checkout, you're receiving an error.

The first issue is really simple to get around.  There are two options.  The first is that you clean up your existing table (within ArcMap) so that all current values within the fields containing domains match the coded values from the domain.  In your Yes or No field, you must have values which don't exactly match.  This could be features with Y, N, yes, no, etc., when they are probably supposed to be "Yes" and "No".  The second option would be to uncheck the box in the Get Data for ArcPad Wizard - Select Output Options page which says 'Validate feature classes before checking out'.

The second issue could potentially be more troublesome, especially without knowing what your custom forms are doing.  You mention that you're using related tables.  Does your script somehow create these relationships or are you using the out-of-the-box functionality?

If you're using OOTB functionality, you need to have both the feature class and related table within the map document before you check out.  Additionally, what cardinality is your relationship, one to many?

My guess is that these errors are not an artifact of the geodatabase schema itself, but rather your customized axf file.  Do you know what exactly these customizations are doing?  Do they simply alter the look and feel of the edit form or are they assisting in additional functionality?

If there are scripts involved, it would be helpful to see them which could potentially lead us in the right direction.  Can you upload the axf file here?

[MatthewCarey]

Thanks for the clarity!

After receiving some very helpful offline assistance, this is how it turned out (definitely more to do with details):

1. Validation errors were found and corrected. There was a discrepancy between the domain assigned to a field in the main feature class and then within Subtypes, if that makes any sense. One was Yes_No while the other was 1_0. For some reason the version 7 check-out tool seemed to let it go but the version 10 one caught it.

2. Re. the custom form, my VBscript referred to data tables by name that are generated as part of the axf. It seems that the version 7 check-out tool and the v10 tool create tables using slightly different naming conventions, and in one case the v10 tool split the data into 2 tables where the v7 tool only generated one. It was a slightly laborious but straightforward task to correct this and get it working.

Very glad the forum was there to help with my newbie issues.