Latest Contributions by DanielleHartman__GISP

This functionality is available when your data is set up in a geodatabase with attribute domains. ... View more

The kind of control you describe is available with layer definition queries. Besides editability, definition queries also have the advantage of being stable if the number of features changes in the underlying data. I would only use "Create Layer From Selected Features" for simple or one-time-only selections. For more complicated selections, it is easy enough to add a flag attribute to your data to use with definition queries. A small joined table with just the desired feature IDs also works. ... View more

Yes!  Same idea as https://c.na9.visual.force.com/apex/ideaView?id=08730000000bmfwAAA. ... View more

Yes!  Same idea as https://c.na9.visual.force.com/apex/ideaView?id=08730000000brLXAAY. ... View more

Yes!  Preserve the Rematch field display settings within a project.  This is so poorly designed it feels like a bug. It makes me hate geocoding. I asked about this at the 2012 UC and they said to post on this site.  This idea needs more votes! ... View more

I also have a project with layers linking to a common table, but in this case there are mutiple layers connected to multiple common tables. Our old ArcPad 8 application used custom scripts to write data to the tables, and there was a lot of post-processing after check-in on the desktop.  For ArcPad 10, we wanted to take advantage of the related table functionality, so we redesigned our geodatabase schema. There are now separate copies of each table linked to each layer. During check-in, there is a simple tool that appends the data from the appropriate tables back into the master table. This was the best solution in term of record management. But the AXF file is rather large, and is running slower than the old application. With just one table, I think a similar approach would work out well. ... View more