Dynamic Geocoding won't update.

[IanBailey]

I created a dynamic geocode in a file geodatabase, but when I append new records to the original table in the file nothing happens to the dynamic geocode point file. I tried it both outside and inside an editing session. And neither works. Am I missing a step?

[ToddSmith]

Charlie, did you ever get this working?  I am trying to do something similar and I am not able to register the linked SQL Server table with the Personal Geodatabase.
Thanks,
Todd

[Mtclimber03]

Todd,

I was not ever able to get this to work. Based on more reading and research it seems apparent that this is not possible. The best I can understand is that it provides one more reason for us to use sde. My next step is to try this with a stored procedure inserting new data into a table on the underlying SQL on the sde database. I'm about 99.9% sure this method will work.

-C

[ToddSmith]

Thanks Charlie, based on the research I have done I don't think it is possible either.  It is too bad because most database tables that organizations want to geocode reside in other systems/databases and not in GIS.

[LakshmiSankaran]

Has this been successful - automated geocoding of a SQL db via SDE? We are in version 10 SP1. Thanks

[NancyGnanicys]

I found this posting which may explain why adding new records to the table via SQL/Access Linked table may not be working.  It appears that the table's new records must be added in through arcgis rather than front end access according to my findings in the forum. 

I am trying to do the same thing with a table in Arcsde 10.0 sp 5, I have established a linked table connection to it through MS Access 2003.  Anytime a record is updated or added/deleted in Access, it reflects the changes immediately in Arcmap's table (upon refresh in Arcmap).  I ran 'dynamically geocode table' and stored it within the same sde geodatabase but the table does not geocode when new features are added of course since they are added in Access. 

Since arcgis needs to append the new information to the table in order for dynamically geocoded table relationships to work, what tool/or idea could I use so that only the new records that are added in get appended to my table with the dynamic geocoding relationship?  Even better is if this could be automated.  I haven't done much python scripting or code programming so if it's possible, could someone point me down the right path to start this?  The existing table records are not edited, just new records need appended then geocoded automatically so a web application can just push it out to users.

http://forums.arcgis.com/threads/23303-How-to-geocode-addresses-dynamically?highlight=dynamic+geocod...

[AllisonPlummer]

Apparently I had an address locator that was looking for a zone field. I didn't have a zone field in my table and I assumed I could just leave the zone field empty and it would ignore that when geocoding. It did work to geocode but was stopping the dynamic functionality. I added a zone field and set it for a blank space so it wasn't NULL and that fixed the problem. Thanks Brad.

I had this problem also. My address locator wanted Address, City, State and Zip. I did not have a state field, which was fine to just geocode, but did not work dynamically. Once I added the State field, it started working (also after hitting the refresh button). For anyone troubleshooting this issue, it seems like having a field for all critera of the address locator might be a good first step.

[Mtclimber03]

Hey guys,

The way I finally resolved this issue was to build a model that would essentially copy a native SQL table to a standalone SDE table that is connected to a dynamic geocoding service. Apparently ArcGIS needs the table to be registered with the geodatabase in order for the dynamic "eye" watching the table to see changes. My model first "deletes rows" then runs an "append" of the SQL native table to the SDE table. With this model exported to python script I was able to build a nightly task in windows task scheduler. This is what dumps the new data over from the native SQL table, then activates the dynamic geocoder, and finally updates the associated feature class.

Hope this has been helpful for you guys out there looking for an answer to similar problems of having live data from another DB connected to dynamic geocode.