'MS Access Table converted to SharePoint list - don't need autonum ID field

Realizing that I can work with linked tables pretty effortlessly, I'm converting one table from MS access to a SharePoint list with the intention of using my MS Access form and database no differently than my current convention. Table name is tbl_061305 and the MS Access form is called frmSLIR with many related tables that I will also be converting to SharePoint lists. I do many operations using vba on my table. One of those is to temporarily work on only one record in a local carbon copy of the table. So, in this case, the SharePoint list will need to have a carbon copy of tbl_061305 called tbl_061305_TEMP

I am aware that SharePoint creates extra fields like Title, Compliance, etc. But I'm not so sure how I should go about my temp table convention. Do I create the same extra fields that SharePoint creates? Do I simply hide them in SharePoint? One field in particular that I do not want to use is the AutoNum ID field that SharePoint creates. I guess I'm fine with that as long as I know MS Access won't require me to adhere to respecting the ID field because I have my own primary key which is generated via code.

Doing a simple test of adding a record with my form, I am confronted with MS Access not knowing what a particular field is. Looking at the error message, it refers to one of the fields that SharePoint adds. So I figured I would add all of the fields to my Temp table that SharePoint adds. But this hasn't fixed the problem. That was just one way I thought of correcting the problem. I haven't yet addressed different ways to fix this.

Please suggest what to be aware of in this SharePoint MS Access integration, going forward.



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source