[AccessD] Access as web front end

Gustav Brock gustav at cactus.dk
Fri Mar 11 08:48:14 CST 2016


Hi Susan

Keep this list from Jim for future reference.

You may add that - for a single user - "terminal services" needs to be nothing more than a simple workstation with remote access which you access via Remote Desktop.

/gustav

-----Oprindelig meddelelse-----
Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne af Jim Dettman
Sendt: 11. marts 2016 15:41
Til: 'Access Developers discussion and problem solving' <accessd at databaseadvisors.com>
Emne: Re: [AccessD] Access as web front end

Susan,

 There's a lot of confusion in this area, in no small part to Microsoft going in different directions and calling everything by almost the same name.

In terms of running Access as a Web App:

1. "Web databases" - Found in A2007/A2010 - Publishes to SharePoint, Access Services in SharePoint required.  Uses SharePoint lists to store data - very
inefficient.   Somewhat like desktop apps (you can use the same DB both on
the desktop and in SharePoint), but no VBA allowed.

2. "Web Apps" - Found in A2013/A2016 - Publishes to SharePoint, Access Services in SharePoint required.  Uses Azure DB to store data if on-line,
SQL 2012 if on premise.   Nothing like desktop app (cannot use a web app on
the desktop). Again no VBA allowed.  Still very limited.  Basic CRUD operations is about it.

 Good overview of what you can do with it is here:

 https://msdn.microsoft.com/en-us/library/office/jj250134.aspx

 What's better about this though is that you can point a traditional Access Desktop app to the same data store, so you can now have multiple front ends for your app.

Web DB's/Web Apps aside, the other options for running a desktop DB on the web "as is" are:

1. Use terminal services, possibly in conjunction with Citrix.  Use your desktop DB more or less as is and everyone remotes into the TS server.  That can be in the form of an icon on their desktop, which they click and the app appears just like any other.

2. Use www.eqldata.com.   

  This is a subscription service.  What they do is two-way replication with your app through a plug-in.  They host the web side and you keep the desktop
side.  OK for a few remote users, but could get pricey if many.   Saves you
from running a TS server though.

HTH,
Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Friday, March 11, 2016 08:25 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Access as web front end

"I used a MS Access developer to create a management tool that I want to host on a PaaS. My frontend is Access and Backend is SQL Express. I want to host this software as a SaaS type service. To do so, I need remote license.
My question is this: Is MS Access front end competitive with other web front end software tools on a hosting environment in your opinion. Look forward to your answer."

This is from a reader. I am so far removed from this type of development now that I can't even respond - want to have a discussion? 

Susan H. 



More information about the AccessD mailing list