Does anybody know what happens if I check out the data from my database, copy it to different GPS devices, collect data in the field, and then try to check the data back in to database? As we have several people working in the same area on the same project, this is what we intend to do.
ArcPad functions under the context of, "Last edit in wins".
You can put an identical copy of an axf on as many devices as you want and check them all back in to the geodatabase. As long as they are only new features, you won't run into any problems at all. The only potential issue is if you check out existing data and either modify the attributes, spatial location, geometry, or delete the feature. In this situation, the last edit made to an existing feature that you check in (if, for example, two field crews edit the same existing feature) will appear in the geodatabase.
ArcPad functions under the context of, "Last edit in wins".
You can put an identical copy of an axf on as many devices as you want and check them all back in to the geodatabase. As long as they are only new features, you won't run into any problems at all. The only potential issue is if you check out existing data and either modify the attributes, spatial location, geometry, or delete the feature. In this situation, the last edit made to an existing feature that you check in (if, for example, two field crews edit the same existing feature) will appear in the geodatabase.
You should be able to leverage the features of the ArcGIS Geodatabase to make life a little easier...
Using a Replica Geodatabase allows for multiuser editing and provides a mechanism to synchronise edits.
I do not recommend that anybody should be using the ArcPad Data Manager to Check-In any edits directly to their Production Geodatabase.
Use Versioning and Replica Geodatabases to check-out and check-in your data, then synchronise the replicas back into your production geodatabase to review any edits before committing changes.