Hi,
I have a regular access database that I have been working on for some time now. I was wondering if it would be possible to get it linked up to sharepoint so people can use it without having access installed on their machine. I tried googling this and it seems that the only way to do it is with a web database, which i found out is entirely different from a regular database. Is it possible to convert my database to a web one in order to host it on sharepoint? I tried copying all of the tables/forms onto a blank web database and it doesnt work because you cannot manage relationships when creating a web database. I think i would have to manage them using data macros or something but i am unsure as how to do that. If anyone can help with this issue then I would be extremely grateful!!
Are referring to the new Web App introduced in Access 2013?
You will need Access 2013 and either Office 365subscription plan with hosted Sharepoint or a SharePoint 2013 Server configured for Access services.
I would not recommend using the Web stuff in the versions prior to Access 2013 and Sharepoint 2013.
Now for the bad news well put by Gina Whipp on Microsoft Answers:
Well, sorry to say but no, you do not convert a database to a Web App and there is no *conversion* that does that. In most cases it's a complete rewrite because no VBA. AND, there is no way to use an .MDB as that is pre Web App. Web App didn't even make their debut until Access 2013. (Well, in Access 2010 but I didn't count that because not a Web App.) So, basically, you would be creating a *fresh* Web App.
Can you answer yes to all of the following:
1) You have Access 2013 and Sharerpoint 2013 with Access Services configured
2) You have the time and money to invest in rewriting your front end. Learning all the new ways to do stuff in a Web App, Figure out how to replace all the VBA code with Macros.
3) Your target date for going live in production is about 12-18 months form now.
If you answered yes to all the above then these may help net you started:
Converting an Access Database to a Web App – Tables
Get started with Access 2013 Web Apps
Alternatives I use:
With the following options you can be live with complete functionality in a matter of days or less.
) Use the Free Access Runtime version on PCs that do not have a full Access license. Most of my clients that run my commercial (shrink-wrapped) solutions not not own Access. Some have only the version of Office that does NOT include Access. I simple install the Access Runtime.
** You should test your front end in Runtme mode. The changes required to be runtime compatible are minimal. If you have already developed you own custom Ribbon then you may be ready to go.
2) Use Thin Client. There is nothing that need to be changed in your front end. I have been running my Access apps over the internet (not web) since 2000 using Terminal Services. I also have clients that run all the Office app including my Access apps on an internal Terminal Server. Some even use the free Access Runtime (option 1 above)
With either of the above option you do not have to convert your front end to a Web App. You get the full functionality and power of the Desktop client.
For me I am converting all my Access back end to Microsoft SQL Server Express. I am dowing more that just moving the tables. If I need a front end that running in a web browser I create it with .NET. It shared the the same SQL Server Back end. This allows me to easily use both Access and ASP.NET together.
