I'm more than curious about the syncing with SQL server....what components/version of FMP do you have on the server/mobile client? This is something we're starting to get into....we've got the linking of ESRI and non-ESRI SQL tables pretty much solved. On that note: use the GLobal ID GUID in your spatial location table as a primary key to relate it, via SQL or some other app, to your non-spatial data table. DO NOT USE ESRI to manage the relationship, and you can avoid the burdensome OID restriction. The only drawback is that this requires a new location to first hit the ESRI location table to generate the UID, which can be dealt with by tinkering with the syncing from the FMP device to force two sync calls: One for new locations which will bring locations from FMP that have been entered in say, lat/long, which then create your location objects with the OID and a UID; then another call to add/update related location information, which cursors through new or edited non-GIS rows based on the UID PK/FK. Complex...sort of...which is why I'm interested in the details of how you're syncing FMP to SQL.
