Migrating Access database to sharepoint

2017-08-29

Question

_{Tuesday, August 29, 2017 2:51 PM}

I have created a small database in access and want to make it online. Sharepoint seems to be a good option. I've registered for office 365. My database is in access file, but now I'm lost and don't know how to convert it into sharepoint database to make it available online for other users. I'm new in this field and trying to make sense of everything. Any help or guidance will be appreciated. Thank you

All replies (5)

_{Tuesday, August 29, 2017 4:18 PM}

To migrate the Access tables to SharePoint lists, within Access --> Export / More / SharePoint list.

None of the other objects are migrated to SharePoint, so if you want to continue using the objects, they would stay within the Access database, and you would base these objects on the lists linked from SharePoint.

Should you want to employ the Access Database, then each user will need to keep a copy on their local machine. You can keep the "master" in a document library, but the user should download the latest and use it locally.

What's your end goal?

Steve Clark, MCTS
Easy Bins Roll-off Dumpster Rentals in Northern VA
Specializing in:
Driveway-sized, roll-off dumpster rentals in Fairfax VA | Dumpster Rentals for Junk Hauling in Springfield VA
Roll-off Rental Dumpsters in Annandale, VA

_{Tuesday, August 29, 2017 5:14 PM}

I spoke with someone at office 365 and they said I need to use a sharepoint app. Access database cannot be migrated into share point any more. So now I'm searching for an app that would match my requirements. I'm hoping to upload my tables and forms into the app.

My end goal is to make a simple database available online for all the users. I just want to make sure that I go in the right path to accomplish it.

_{Tuesday, August 29, 2017 5:46 PM}

The Access WebApp is fairly well documented as to how to setup and implement, but I highly doubt that you "need" to use it.

First, it's pretty weak sauce. For starters, you can't use Action Queries. So, if you can't use the most powerful feature that Access has to offer, then why bother? Just jam the data in SharePoint lists and move on. (This isn't something they print on the glossy marketing brochures.)

Second: "Microsoft no longer recommends creating and using Access web apps in SharePoint. As an alternative, consider using Microsoft PowerApps to build no-code business solutions for the web and mobile devices."
https://msdn.microsoft.com/en-us/library/office/jj249372.aspx

(Pretty ironic that this page says Don't use it, but they're still trying to convince you.)

Tell me what your application does, and how you envision it in a multi-user online environment, and I'll help you construct a solution. (I'm fairly confident that the answer won't include the Access WebApp.)

_{Wednesday, August 30, 2017 2:49 AM}

You are right! I'm not relying on Access webApp any more. I'm starting everything from scratch in Sharepoint, and making use of infopath design.

Before starting my project on Access I did online research and totally got misguided. I thought migration will not be a problem.

The database that I'm creating is fairly simple. I have 4 table and two search forms that search some of the fields from those 4 tables.

_{Wednesday, August 30, 2017 12:09 PM}

Only because of the threat of needing mobile/BYOD solutions, would I look to see what PowerApps has to offer. I never got into InfoPath, and thankfully it's going away, but you'll probably end up using IP.

Share via

Migrating Access database to sharepoint

Question

All replies (5)

Additional resources