I was able to test this bug and found that the problem was with both the data and the code.
I went to mapindex 15S02W00 and created a new taxlot. The taxlot didn't get any attributes. This turned out to be due to the fact that the MapIndex.ORMapNum field was set to "00S01.00W0000--00". This is an improperly formatted value. It should be 24 characters, but is only 22. The value should be...
Per my (accidentally anonymous) followup below on 2008-10-07 09:08, the easy fix for this is a geodatabase change. I am making a corresponding code change for a future release that will handle it more gracefully when this fix is not in place. Note: This fix works in 9.2 SP5 and 9.3 SP0. It should work with SDE as well as Access GDBs.
Item #1 has been removed from the spec for this project based on tools committee review and discussion. Items #2 and #3 have been renumbered to #1 and #2. The attached project spec file has been revised.
File Added: SettingsEnhancementProjectSpecification2.doc.
1. When editing ORMAP editor extension settings, it is possible to enter invalid values (e.g. not just incorrect, but of the wrong format). There is currently no validation on the settings input fields.
2. When importing these settings using the Import button the user needs more flexibility to load from settings files with different names (e.g. DOR users could load files for different...
