Follow on from a prior question on an issue with an Access db back end having ID field conflicts. Suggestion was to move the Access tables to SQL first, that this would preserve the ID fields in the numbering scheme that is lost when using the Access to SharePoint export tool.
Goals are 1) to moves ~12 tables with ~1,600 records to SQL on the SharePoint lab machine, 2) Present the tables in SharePoint lists for view/edit etc. as they would be if exported via Access and 3) Continue to use the current Access front end connecting to the tables in SQL in place of the current Access tables back end.
Since this is really a three part question; can we start by asking the first obvious, which is "is this possible/best solution?" All is lab right now but as you all know even building a SharePoint lab is crazy time consuming, so if a great risk, shoot the idea down would be an acceptable answer, with extra "points" for an alternative idea.