AXF file crashes ArcPAD in the mobile device

[ClaudiaListopad]

I am running ArcGIS 9.3.1 and ArcPAD 10.0. I have created a personal geodatabase that has 11 feature classes and multiple related tables for these layers. It is a somewhat complex database, but the relationships are crucial, since they are 1-many. When I check this geodatabase out for ArcPAD it created an AXF file that is about 10 MG in size, which I know is reasonably large. The AXF file works fine (all the related tables are there) in the ArcPAD in the desktop, but once I try to open it on the mobile device (a Nomad), it crashes the project. I tested shapefiles and larger rasters in the mobile device by themselves and there are no issues opening these, even ones that are bigger than the AXf file.

Is there some size limitation on what we can bring in as an AXF file?Any ideas of work-arounds? I could use studio and customize the forms further (some fields do not need edited in the field), but wll this decrease the overall AXF file size? I need the keep the data in geodatabase format, since there are 1-many related tables.

Thanks!

[StevenRehbaum]

I have done quite a bit of testing with .axf files and reached some conclusions regarding our hardware specifications:  http://forums.arcgis.com/threads/14015-Bug-Report-Bug-with-axf-Files-Confirmed-in-ArcPad-10?p=48842#....  This data came out of SDE, but the result was the same out of a .gdb.  My issue was domains and subtypes making the .axf pretty big.  My thought is our Recon lacked the RAM to open an .axf with all of the data.  Related tables are probably have the same effect on the .axf output.  I went back to shapefiles and wrote a check-in script that basically does the same thing (maybe slightly better as I added a couple of bells and whistles) as check-in and seems to work perfectly.  I haven't given up on the .axf as it would save a great deal of time when changes to subtypes and domains are needed (modifying each .apl), but for now, we cannot use it at all with our asset management schema.  Good luck.

Greetings former GPIer!

[ClaudiaListopad]

Greetings, former GPIer! I am glad you said something, I don't usually look at the usernames. I have lost your contact through time, and tried to find it, so send me an email Steve (clistopad@appliedecologyinc.com).

Now, regarding my issue, how will converting to shapefile work, since related tables no longer can be brought it? The field staff, in my case, will enter some of the related table data in the field. I am hoping ESRI support has another workable solution, but I am concerned after hearing this from this forum. It sounds like a tablet or laptop would run this AXF without any issue, but Nomads were purchased for this exact purpose.

I appreciate any other experiences from others out there that used AXF files. Thanks!!

[StevenRehbaum]

Greetings, former GPIer! I am glad you said something, I don't usually look at the usernames. I have lost your contact through time, and tried to find it, so send me an email Steve (clistopad@appliedecologyinc.com). 

Now, regarding my issue, how will converting to shapefile work, since related tables no longer can be brought it? The field staff, in my case, will enter some of the related table data in the field. I am hoping ESRI support has another workable solution, but I am concerned after hearing this from this forum. It sounds like a tablet or laptop would run this AXF without any issue, but Nomads were purchased for this exact purpose. 

I appreciate any other experiences from others out there that used AXF files. Thanks!!

Sorry if I wasn't clear. I went back to shapefile because of the limitations of the .axf in file size. In your case, I recommend you break your .axf into multiple .axfs and .apms if feasible and eliminate (or uncheck in the .mxd) all unnecessary fields. I would have used this approach, but I have custom dropdown custom toolbars that are partially driven by GPScorrect and my field staff cannot make changes at all to the prefs or anything else (intentional).

I thought I was going crazy when I could open my .apm with the large .axf no problem on my desktop and then it spun the loading wheel on the Recon forever. The primary difference seemed to be RAM (per my comments in the other thread). I tested it on a laptop and no problem either. Here is what a colleague sent me regarding this (all pretty obvious, but I thought I would pass it along):

â??I'm not sure I have a specific solution to anyone's problem here, but I figured I'd chime in and share my particular experience with ArcPad and the GeoXH


Our project recently began GPS collection of surface communication features (Poles, Manholes, Pedestals, etc). We are using a Trimble GeoXH GeoExplorer 2008 series GPS unit w/ the latest ArcPad 7.1.1. Having no prior experience with GPS I did some research, read the manuals, borrowed a Trimble training manual (from an instructor-led course) from a friend, and set up our whole process. Here is what we do:

-I do daily check-outs of 8 editable features. For editable features I only check out the SCHEMA to edit. For the 3 background info layers (streets, buildings, parking lots) I COPY OUT data which creates Shapefiles of the area they'll be working in that particular day.

Sometimes they cover a larger geographic area so the background Shapefiles are larger. On those days they say the unit tends to run a little slower.

Some things I learned through the setup process:

-Don't check out too many editable features. Initially I checked out our entire database (~40 features) and it would take 20+ minutes just to load the map.


-Filter out the fields you don't need by un-checking them in the Layer Properties in ArcGIS. Having too many fields in the AXF just mucks up the works and makes the Attribute Window load slower

-If multiple features are configured in a particular way with a SubTypeID field it'll get 'mixed up' in the AXF. I had fiber_line subtypes showing up under the utility_pole featureclass domain dropdown. I'm not too clear on the configuration I didn't design the database we work in (using SDSFIE) but if you set the "Subtype Field:" to None in the Feature Class Properties box in ArcCatalog it should take care of it

-DO NOT create topology in the same database your check in/out of!!! It totally breaks the check in/out process.

-Like was already stated here, using a SD memory card seems to slow down things significantly. If you need more than the onboard storage consider trimming down your process somehow"

So limiting fields, subtypes, and domains all greatly reduce the size (among other things like related tables it sounds). I would try multiple .axfs and .apms to start with along with limiting to necessary fields for collection only. You might only have to only break it in half (fingers crossed).

I didn't know about the .axf issue until well into developing our database. If I knew the .axf with all of our subtypes and domains did not work initially, I would of spent far less time diagnosing the problem and had field units up and ready. I did use the ouput .axf to create all the .apls for the shapefiles (ArcPad Studio), but still had to create all the lookups for the coded values of the domains as well create the subtypes. That is pretty time consuming when you have 34 layers to do.

I know I am not the only one around here who has had issues with .axf files. I am really hoping this issue is resolved sooner than later. Best of luck.

Steve