Why I STILL Love Access

Here's to Access, My BFF

Access has been very, very good to me. For at least the last 10 or 12 years, it's paid my rent, contributed to my daughter's college education and helped me put on a few pounds too many at the dinner table. And that's just the monetary side of things. There's also the on-going personal satisfaction of facing a new challenge from a client, or from a poster on Utter Access and finding that you really CAN do most things with Access.

Hammers, Rubber Washers, Lug Nuts and Lookup Fields in Tables

Many, many years ago, I learned The First Three Rules of Plumbing.

1. Never start a plumbing project after all the hardware stores have closed.

Migrating Larger Tables to SharePoint

This is the third, and possibly the last, in a series of blog posts on my experiences migrating data from a working Access/SQL Server database to SharePoint, where it now serves me daily. It's a "hybrid" database, in the sense that the Front End is the original Access accdb, complete with all of the original VBA intact, while the Back End lives on SharePoint.

Patching Up Relationships On SharePoint Migrations

In my last previous blog post, I described one of the problems with exporting existing tables from Access or SQL Server to SharePoint. SharePoint bumps the existing Primary Key field out of its way and replaces it with a new one which SharePoint generates in its place. Here’s how that looks.

Disappearing Primary Keys Notwithstanding, You Can Migrate to SharePoint

Recently, a poster at Utter Access asked for help moving Access tables from an existing database to SharePoint tables (or more accurately, to SharePoint lists). His goal was to link to those tables in a Hybrid Access database. One of the issues raised was the supposed limit on the number of records you can export. Fortunately, a couple of really knowledgeable people, Albert Kallal and Bonnie Hicks, stepped in and helped address the poster’s questions.