Solved

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

Posted on 2013-01-04
2
278 Views
Last Modified: 2013-01-05
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?
0
Comment
Question by:VirtualKansas
2 Comments
 
LVL 74

Assisted Solution

by:Jeffrey Coachman
Jeffrey Coachman earned 250 total points
ID: 38745158
We are currently going through a similar scenario.

If this is a standard .mdb file (access 200 format)
...and it is working just fine.
Then I would really suggest moving it up to the .accdb format in order to work smoothly with sharepoint.

But before you think about Sharepoint, you should clearly define what you mean by:
"company is growing and outgrowing access. "


Sharepoint seems like it is maturing, but it is not a simple product to set up. (especially not on the MS Access side.)
Access in sharepoint can be a confusing mix of Web Databases, Workspaces, Sharepoint Lists, Web Forms, Publishing to SP, Saving To SP, Web Forms, ...etc

This all before the confusing mix of steps to actually make the db easily accessible to the end users...


Just my thoughts on this.

Let's see what other experts post...

JeffCoachman
0
 
LVL 57

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 250 total points
ID: 38746676
Ditto Jeff's comments on Sharepoint.

However what I'm wondering is if you have considered moving to Access FE with a SQL server backend.

  There's no limit then on connections or size of the database, and you get to retain virtually all of your code to date just the way it is.

Jim.
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Correct ordering 16 48
ms/access report does not open query 20 33
Syntax error with between dates 6 19
Multiple queries for a form 14 22
This article is a continuation or rather an extension from Cascading Combos (http://www.experts-exchange.com/A_5949.html) and builds on examples developed in detail there. It should be understandable alone, but I recommend reading the previous artic…
I see at least one EE question a week that pertains to using temporary tables in MS Access.  But surprisingly, I was unable to find a single article devoted solely to this topic. I don’t intend to describe all of the uses of temporary tables in t…
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now