
Trusted by 500+ businesses to solve complex database challenges.
A services company in the oil industry in Alberta, Canada was using an Access database that was working well for them. They wanted to move this database online to Sharepoint, so they could utilize the database in multiple locations. There are a lot of options to make an online database. We can help you understand the best option for your needs. The tricky part of this project was to convert all the data macros the original developer put on a few tables. This is a big problem with Microsoft template db’s. These are nice if you use them exactly the way they are built, with no need to customize (which is rare). But unfortunately, they are very difficult to customize.
Once the table macros were reworked, field offices in Alberta could update the same lists head office relied on without emailing spreadsheets back and forth. Access stayed in the picture for the heavier reporting and forms their managers already knew. SharePoint handled the shared data. That hybrid setup is what many multi-location clients end up with.
This was an 8-hour project because the database was already working. The time went into untangling template macros, not rebuilding from scratch. If your Access file came from a Microsoft template and you need to change how it behaves, expect that kind of cleanup before any online move.
Moving online is not one-size-fits-all. SharePoint, split database on a server, and other options each fit different teams. We will walk through how many users you have, where they sit, and what must stay in Access before recommending a path. No sales pitch for the wrong architecture.