Avatar of VirtualKansas
VirtualKansas
 asked on

Legacy Access database with a table having ID's in a key field

OK EE; here's the back story:

Inherited a very well developed Access database.  Construction started in ~2000 and queries,  forms & reports have been building ever since.  Again, its well built and it has been repurposed for many like projects for the better part of ten years.  The database was properly split with tables on the back end and a well formed user interface for local machines.  All is well, but here's the thing; company is growing and outgrowing access.  We are lab testing SharePoint as an alternative with moderate success.  We're not convinced SharePoint is the way to go and we are looking at Filemaker as the real need for 90% of users is reporting and not data entry.

Now, the question/issue; using Access services in SharePoint is a flop given the vintage of the database.  Too many issues with the queries & reports not being web ready.  Strike one SharePoint.  But, we have hade moderate success testing the importation of just the tables and allowing the front end of access connect, with one exception, leading me to the issues/question:

There is a simple 13 record table that is very linked up in all forms, queries & reports.  The primary key in this table is headed as "ID" and to make matters worse, when the db was repurposed, the ID's sequence started after the last old record was purged.  This makes the first ID start at 37 and not 1.  So of all things that went well in the test conversion to SharePoint, this one table caused SharePoint to create a new column labeled "_OldID" and the standard "new" ID column in SharePoint started numbering 1 to 13.  This of course blows up all the queries, etc. in the Access front end, as they do not recognize 1 to 13.

So, the actual ID values in the original Access database are intractable in order 37 to 49, while the SharePoint "new" ID's are intractably set from 1 to 13.  I would like to attack this at the SharePoint lists (tables) if possible, up to and including scrapping SharePoint and using Filemaker.

Short version?  Is it possible to change the ID values in the SharePoint list? (it’s a one time thing so manually is OK.)  Or is there some magic that can be done before importing the tables to get ID numbers set like for like?  Or, scrap the project and got to an alternative for web reporting from the vintage access database?
Microsoft SharePointMicrosoft Access

Avatar of undefined
Last Comment
Jim Dettman (EE MVE)

8/22/2022 - Mon
SOLUTION
Jeffrey Coachman

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
ASKER CERTIFIED SOLUTION
Jim Dettman (EE MVE)

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck