Thanks for the overview. So, I may be able to use the personal geodatabase if wanting to edit through Access, although I'll run up against all of the personal gdb limitations. I've used these in the past, but the table was outside of the database, and a model imported to the gdb, following edits. This is apparently something I'd like to avoid. So, I most likely will need to utilize the SDE gdb, and sql studio to edit, and ultimately generate forms. Is it as easy as opening up sql studio, and linking to the table within the sde gdb, or am I missing a step somewhere?
All of these interactive gdbs' are linking to jurisdictional or environmental boundaries using a one to many relationship. The many being the table, and the boundary being the one. Do you feel building relationship classes is the best approach? The results will be put on a service, with built in queries and reports, although I've run across many issues with displaying/labeling the results of a query where a 'many' table was used, and a 'one' was the geographic component... Thanks again! All the best!