How to convert Access database to a web app?

I have an access database I would like to make accessible online. Is Sharepoint the best way to do that? Is there another way by converting the Access database to SQL?
brasimanAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Jim Dettman (Microsoft MVP/ EE MVE)Connect With a Mentor PresidentCommented:
<<I have an access database I would like to make accessible online. Is Sharepoint the best way to do that? Is there another way by converting the Access database to SQL?>>

  Just to add/clarify a few things:

"Access is not optimized to use SQL Server (or Azure) over a WAN.  You could do it but it would probably involve massive changes to convert the forms from bound to unbound. "

 While that first part is true, there are things you can do to make it work fairly well.   JStreet technologies has done quite a bit of work in this area, and offers some tips and tricks for making that happen:

"Best of Both Worlds"
http://www.jstreettech.com/downloads.aspx

But that leads into the 2nd part; changes are required, almost to the point of a re-write in some cases, which as Pat said, would be considered massive.  it really depends on what/how much of the app you want to make available to users.   It's something you should not dismiss right off.

Access 2007/A2010 Web Databases use SharePoint lists for storing data, and that is a non-starter.  As Pat pointed out, SharePoint lists are not a great way to store relational data.

Access 2013/2016 Web Apps use SharePoint for a the Front End, and Azure for a back end to store the data (SQL Server in the Cloud).   This works well.

But in both cases, these Web versions are "Access" in name only, and are a different animal entirely from a desktop database.  It's not a one for one.  For example, you can't use VBA code in either.

However if your remote users only need basic CRUD (Create, Read, Update, and Delete) of information, then it might work well.   What you do is use the web app for them, and then connect to the Azure BE directly with a desktop database to do everything else (processing, reporting, etc).

 What that looks like is this:
https://msdn.microsoft.com/en-us/library/office/jj250134.aspx

 Your other option is to write a new front end for the web with something like ASP.Net, then point to the back end database that is used by your current app.

HTH,
Jim.
0
 
PatHartmanConnect With a Mentor Commented:
There is no true conversion path from a client/server Access app to an Access web app.

If you need to distribute your app to users not located on your LAN, the far and away superior method is to use Citrix or RDP.  That allows you to leave the app as it is although you could convert the BE to SQL Server if that makes sense.

If you have enough users, it makes sense to host the app yourself.  Otherwise, thee are service bureaus that will host the app for you.

Access is not optimized to use SQL Server (or Azure) over a WAN.  You could do it but it would probably involve massive changes to convert the forms from bound to unbound.  Switching to SharePoint Lists has other problems.  The SharePoint lists are not a true relational database and the performance degrades with more than a few thousand rows in your tables.

If you don't have to make everything available online, you might be able to come up with a compromise that uses SharePoint Lists to pass data between the Access client/server app and SharePoint forms to allow remote users some functionality such as viewing a customer list or part master that the Access app replaces nightly.  Or possibly to do some limited data collection.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Connect With a Mentor Infotrakker SoftwareCommented:
There's this:

www.eqldata.com

They can host your Access db on the web. It's not free, of course, but it's a quick and easy way if you have only a few users.
0
All Courses

From novice to tech pro — start learning today.