I wanted to float something by the community before I set out down this path.
My customer has a need to search one non-spacial table and then "ZoomTo" a related record in a spacial table.
They don't like the related record functionality.
We attempted to setup a view containing both tables but have been thwarted by many complications surrounding not being able to compress the DB currently creating large Add/Delete recs in the Default/Base data set.
So.....
I'm thinking - modify the code to search on the table (just as its doing now) but.. once the recs are down, I re-query the spacial table for the matching recs - then send to the result list.
Thoughts?
My customer has a need to search one non-spacial table and then "ZoomTo" a related record in a spacial table.
They don't like the related record functionality.
We attempted to setup a view containing both tables but have been thwarted by many complications surrounding not being able to compress the DB currently creating large Add/Delete recs in the Default/Base data set.
So.....
I'm thinking - modify the code to search on the table (just as its doing now) but.. once the recs are down, I re-query the spacial table for the matching recs - then send to the result list.
Thoughts?