Hi,
The Update or Add method of EditTools always fails if you try to use an empty, null or otherwise invalid shape. I know that this behavior is by design and prevents null geometries or geographies in a table containing spatial data. However there are many times in our application when we have quite a bit of tabular data about some piece of property and even know its general location but do not have a shape for it. We would like to be able to store this data in our spatial table and add the exact shape later.
We are getting around this by using non-ThinkGeo methods to add or create rows in the table with null shapes. However, it would be very convenient if there were a way to accoplish this within the ThinkGeo framework. Would it be possible, in the ThinkGeo framework, to add a parameter to the Update and Add methods of the EditTools so that null shapes would be permissable? Or is there already some way to do that by extending existing functionality?
Thanks,
Steve