MSAccess needs a web interface. FM Web Direct uses the layouts that can also be used on desktop. Either way, something must be created. I don't know Azure.
-- sent from myPhone --
Beverly - in this case Azure is just MS SQL Server in the cloud.
So an "interface" still needs to be built. I used to use Access with ColdFusion for some web publishing, then we moved the data to MS SQL.
1 of 1 people found this helpful
There are a lot of differences between an Access desktop applications and an Access web-application. For me, the lack of VBA support in the web environment Is a real problem.
Bottom line is you maybe looking at a major re-write depending on the complexity of the application.
Oh ok! thanks for that link. Looks like Web Direct is a winner then.
Doesn't the Web version of Access require a Sharepoint server? I know I looked into it a year or so ago, and it looked very challenging to setup. But I may have been missing something.
I've re-written a number of Access databases into Filemaker, and it has worked out quite well.
Thanks for the comments guys. Just some notes below for others based on copious googling …
Access web apps need Sharepoint online or server. It seems a lot has changed from Access 20110 to 2013 . Now 2016 is coming out. So need we need to be careful to read what is current. Interesting to note Access has been dropped from lower lever office 365 subscriptions. I see you need to use macros instead of VBA .. that is good because thats was all I ever used in Access!
Forums are worth a look too see challenges around web printing and containers as mentioned: http://answers.microsoft.com/en-us/office/forum/office_2016-access/web-database/0fa94ab6-6180-4f21-8648-29882ce0fe7c
You’ve got to check this out for a chuckle. Look familiar: https://access.uservoice.com/forums/321915-access-web-apps/suggestions/10191759-define-a-vision-for-access-web-app-and-stick-with
“Define a vision for Access Web App and stick with it. In Access 2010 you gave us “web” apps based on SharePoint lists. In Access 2013 you gave us a completely new “web” app based on SQL Server and SharePoint. 2010 web apps were completely abandoned. In Access 2016 you gave… well I’m not really sure what you did. After seeing new features to Access 2013 web apps dribble out, there has been nothing released for almost a year. It appears 2013 web apps are going to suffer the same fate as Access 2010 web apps. You can’t keep changing the direction every time the product cycle or management changes, nobody is going to invest in a platform that is abandoned ever three years. I’m afraid it’s three strikes and you are out.”And a massive video that I haven’t watched yet https://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC204
Yes indeed. One of my favorite sayings, "If the grass looks greener on the other side of the fence, you probably need to water your lawn."