Script Error 8004E37

[DonaldVetterling]

I have an ArcPad project that runs fine in ArcPad 10.0.4 but I get the attached "script error 80040E37" when I open it in ArcPad 10.2 on a Win 7 64bit desktop. When I clear the error it seems to work fine. Any thoughts?

[BrysonWebber]

Last time I got a similar error is when we upgraded to ArcGIS 10.1 and it was renaming the length field.  ArcPad didn't like the symbols used in the new default length field.  All I did is hide the field and it didn't export to ArcPad.  Don't know if this is the problem but I would look into it and see if it is one of Esri's default fields that ArcPad 10.2 doesn't like.

Bryson

[DonaldVetterling]

Further investigation into my issue shows that the script error shows up when a feature class is renamed in the ArcMap document and then that feature class is exported to an axf file (editable or non editable).

[mrmark]

Thanks for confirming my suspicions. We just started pushing out ArcPad 10.2 and immediately started seeing this error. It didn't help when I re-exported the files from ArcMap 10.2. After seeing this I asked around and discovered that one of the feature classes had been given a new name in the map document that was different from the actual feature class in the geodatabase.

I think this is a huge issue as this is a quite common occurrence, e.g. feature class is named TDS_union but someone renames it to "Inspection Points" or something in the table of contents.

[MatthewCarey]

I'm getting this error message but it doesn't seem to be related to the renaming of layers.

Here's what I've been doing:
In ArcMap 10.2 (Win 7 64 bit), check out data from a feature class in a versioned 10.1 SQL Server Express geodatabase to an axf file.
On opening the axf file in ArcPad 10.2 I get the Script Error.


But if I do this:
With the same setup, check out data from a feature class in a 10.2 file geodatabase to an axf file.
It opens fine in ArcPad 10.2.

In neither case have I changed any layer names in the TOC; both are simple point feature classes, and I didn't use a checkout template.

Anyone have any further thoughts or different scenarios to offer?

[MohamedNaeem]

I'm getting this error message but it doesn't seem to be related to the renaming of layers.

Here's what I've been doing:
In ArcMap 10.2 (Win 7 64 bit), check out data from a feature class in a versioned 10.1 SQL Server Express geodatabase to an axf file.
On opening the axf file in ArcPad 10.2 I get the Script Error.


But if I do this:
With the same setup, check out data from a feature class in a 10.2 file geodatabase to an axf file.
It opens fine in ArcPad 10.2.

In neither case have I changed any layer names in the TOC; both are simple point feature classes, and I didn't use a checkout template.

Anyone have any further thoughts or different scenarios to offer?

This worked for me: Ensure that your feature class name and alias is the same and DO NOT change it when you drag it into your mxd (feature class name = alias = layer name)

[BarbaraHammond]

I'm having the same issue (10.2.1) and I haven't changed anything in the two feature classes that I extracted (schema only).  The script error appears as a pop-up, but if I close it, the extract does open in ArcPad. However, after I've collected the data and attempt to load the .afx file (Get Data from ArcPad wizard) I'm getting an error message that the .afx file didn't contain a transaction log. Are these two issues related?

[roemhildtg]

Just updated our devices to 10.2 and are currently experiencing this error. Our layers are in a an SDE database powered by Microsoft SQL server. I tried looking into the layer name issue and everything appears the same. As a simple test I added just one layer to the project, exported it directly to arcpad, and opened it up. The same error keeps occuring.

Similar to what another poster mentioned, we are still able to ignore this error and add data, so maybe this isn't an issue worth pursuing.

Any news on this topic?

[MarikaVertzonis]

The dev team have been looking at this and believe its related to the Quick Fields implementation. Changes have been made and will be available in the next ArcPad release. You can confirm this yourself by disabling Quick Fields. To do this, delete (or move to a sub folder) the Quick Fields applet, and re launch your data in ArcPad.

[roemhildtg]

Where do I remove this applet from? We are using the Get Data For ArcPad Extension.