Programmer-analyst

Simon Boutin

<div>
Hi John,<br />
thanks for your fast reply.<br />
<b>VPS</b> stands for &quot;<b>Virtual Private Server</b>&quot; right?<br />
And what &quot;<b>RDP</b>&quot; stands for?<br />
Note in the final solution we must have at least 20 simultaned users connected to the Cloud backend, is that possible with Remote Desktop Services?<br />
Finally, is your solution simple to implement? Because I have no knowledge about that and the complete solution must be successful before 2020...<br />
Thank you very much for your help!
</div>


<div>
Access does not paly well with WANs which the cloud is. &nbsp;Access is meant to be used over a wired LAN,<br />
<br />
I'd urge you to read <a href="https://www.devhut.net/2016/09/24/access-back-end-location-wan-online-server-onedrive-dropbox/" rel="ugc">https://www.devhut.net/201<wbr />6/09/24/ac<wbr />cess-back-<wbr />end-locati<wbr />on-wan-onl<wbr />ine-server<wbr />-onedrive-<wbr />dropbox/</a> which gives a couple options.<br />
<br />
If your client has SQL Server already, or an Azure account, then you could upsize the back-end to SQL Server and go from there. &nbsp;Even if they don't, you could install and use SQL Server Express.<br />
<br />
Almost every solution will involve IT support to install/setup software, access, ... so a deadline of 2020 may not be feasible in any case. &nbsp;It will greatly depend on IT and then you may need to make changes to the database as well.
</div>


<div>
RDP -- &gt;&nbsp;Remote Desktop<br />
I know from a fact that the RDP scenario....works...i had a similar case in my old job and we had quite a few people working that scenario...but i haven't &nbsp;tested the limits.....<br />
Since you are a strict time schedule &nbsp;my best bet is to rent a good VPS...setup RDS ...and just perform all the operations...the trial period should be more than enough to test just about everything...<br />
If you implement the RemoteApp scenario...to the end users it would almost transparent...
</div>


<div>
Before getting into complex scenarios, are all the implicated users connected through a common wired LAN? &nbsp;If so, you should simply be able to split your database and deploy an individual copy of the front-end to each user to use, that's it.<br />
<br />
You may like to review<br />
<br />
<a href="https://www.devhut.net/2017/04/09/setting-up-an-ms-access-database/" rel="ugc">https://www.devhut.net/201<wbr />7/04/09/se<wbr />tting-up-a<wbr />n-ms-acces<wbr />s-database<wbr />/</a><br />
<a href="https://www.devhut.net/2015/06/30/ms-access-deploying-your-database-front-end-to-your-users/" rel="ugc">https://www.devhut.net/201<wbr />5/06/30/ms<wbr />-access-de<wbr />ploying-yo<wbr />ur-databas<wbr />e-front-en<wbr />d-to-your-<wbr />users/</a>
</div>


<div>
<blockquote>
My client is a business which want to do that in order to access its data from everywhere (or at the very least from the company's intranet network).
</blockquote>
In the intranet, having a normal, stable LAN, you use the split database approach, where every user gets its own front-end copied to a local directory and the backend database file resides on a share of the fileserver.<br />
<br />
Depending on the amount of data and the security targets, you need to consider using a RDBMS and use linked tables and views as well as pass-through queries, when necessary. Here the ideal back-end is SQL Server, but Oracle, Informix, Postgres and MySQL are also possible.<br />
<br />
The question is: How much budget is allocated for the &quot;everywhere&quot; requirement? And does it include connected / disconnected access?<br />
<br />
When the users are always connected, then you may use a terminal server to host the application, this gives the optimal experience between application performance and resilience. <br />
When your client offers good VPN to its users, then a on-premises RDBMS works pretty well. In many scenarios better than entry-level cloud databases.<br />
And the last thing which works connected everywhere: cloud database instances. But you need - at least for Azure and AWS - more than the entry level databases. Otherwise your application will have poor performance (experienced lag).
</div>


<div>
Stay away from Sharepoint. <br />
<br />
Azure can work, but unless you've created the application with client-server techniques that often means a full rewrite.<br />
<br />
Your best option is to use an RDS system like Citrix or Microsoft RDS. You can support quite a few users on that scenario, and those users can be located anywhere.
</div>


<div>
Sharepoint is, in this respect, similar to OneDrive, so your question, and thus the answer, is very close to this question:<br />
<br />
<a href="https://www.experts-exchange.com/questions/29166332/MS-Access-SQL-Virtual-Server.html?anchorAnswerId=42992233#a42992233" rel="ugc">MS Access, SQL, Virtual Server</a><br />
<br />
Likewise, consider using the method described in detail in my article:<br />
<br />
<a href="https://www.experts-exchange.com/articles/33417/Deploy-and-update-a-Microsoft-Access-application-with-one-click.html" rel="ugc">Deploy and update a Microsoft Access application with one click</a>
</div>


<div>
Thank you very much for your answers.<br />
At this time I'm not sure which solutions are better until the project is implemented...
</div>


<div>
You need to write down your project specifications (number of users, connection types: wired/wireless, LAN/WAN, access needs: local only, remote, budget, ...) and only once you've properly defined all of that can you make an informed decision on the proper route to take.
</div>


<div>
Number of users = Max 20<br />
wired/wireless = Both<br />
WAN if possible, in the worst case LAN<br />
Access needs = Read/Write<br />
Not local only<br />
Remote = if possible yes<br />
budget = less than 2 000$ if possible<br />
<br />
It's not an absolute certitude, but it's what we have in mind.<br />
You're help is very appreciated, thanks!
</div>


<div>
Truthfully, with requirements like that, (i) the budget doesn't match the project, (ii) I would never consider Access and would be looking at using proper web technologies (PHP, .Net, ...).<br />
<br />
Did you ever review my original link? &nbsp;In it a couple alternatives exists CITRIX, Terminal Services, using external hosting services &nbsp;(for instance <a href="http://accesshosting.com/" rel="ugc">http://accesshosting.com/</a> - one of many, I have to affiliation), migrating the BE to Azure, but they all take time to deploy and in some cases the application itself needs to be adjusted to work properly.
</div>


<div>
WAN is an option if the FE is carefully designed...in my older demo benchmark application :<a href="https://www.linkedin.com/posts/tsgiannis_a-small-demo-of-connecting-ms-access-fe-to-activity-6392696633531858944-dsuU" rel="ugc">https://www.linkedin.com/posts/tsgiannis_a-small-demo-of-connecting-ms-access-fe-to-activity-6392696633531858944-dsuU</a><br />
You will see a pulling of 1000 rows of records of a 120+ columns table in just 3 seconds...all these with a mere ADSL lines around 14mbps with 50+ ms latency on a dead cheap VPS (old deal 1€/mo) with a single Xeon shared XEON with 1Gb memory running MySQL<br />
If you could get finer line with most importantly better ping the operation would be almost natural and if heavy queries are involved it would fly....but it needs works...quite some work.
</div>


<div>
Hi Daniel,<br />
yes I reviewed your original link and take it into account.<br />
I think now I have all info I was asking for.<br />
I think RDS with Citrix is the way I should take.<br />
I talk to my client and the first step will be to implement to a LAN, then early in 2020 we will check for WAN.<br />
Thank you very much everyone for your advices.
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
I'm a MS Access developper who try to put my database backend to the cloud and link it to the frontend on my desktop. My client is a business which want to do that in order to access its data from everywhere (or at the very least from the company's intranet network).<br />
I see blogs and I think the better solution is to use a Sharepoint site but I know nothing about Sharepoint nor to install it, configure it, etc.<br />
<br />
1. Do you know if Sharepoint is the solution to my problem?<br />
2. Do you know how can I get it?<br />
3. Is there exist a better solution to access my backend with my MS Access frontend from the cloud?
</div>
</div>


Hi,
I'm a MS Access developper who try to put my database backend to the cloud and link it to the frontend on my desktop. My client is a business which want to do that in order to access its data from everywhere (or at the very least from the company's intranet network).
I see blogs and I think the better solution is to use a Sharepoint site but I know nothing about Sharepoint nor to install it, configure it, etc.

1. Do you know if Sharepoint is the solution to my problem?
2. Do you know how can I get it?
3. Is there exist a better solution to access my backend with my MS Access frontend from the cloud?

MS Access backend on the cloud

Microsoft Sharepoint is a software platform and family of software products used for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence and collaboration. SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite.

Microsoft SharePoint

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.

Databases

Installation is the act of making a computer program program ready for execution. Because the process varies programs often come with a specialized program responsible for doing whatever is needed for their installation. Installation may be part of a larger software deployment process. Cross platform installer builders that produce installers for Windows, Mac OS X and Linux include InstallAnywhere, InstallBuilder and Install4J. Installers for Microsoft Windows include Windows Installer, InstallShield, and Wise Installation Studio; free installer-authoring tools include NSIS, IzPack, Clickteam, InnoSetup, InstallSimple and WiX. Mac OS X includes Installer, and also includes a separate software updating application.

Installation

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

A blog is a discussion or informational site consisting of discrete entries ("posts") typically displayed in reverse chronological order. Blogs can be the work of a single individual but more recently "multi-author blogs" (MABs) have developed, with posts written by large numbers of authors and professionally edited and "microblogging" systems help integrate blogs into societal newstreams.