Question Strategies for Multiple Clients to Use an Access System

[Solar.Paul]

I am interested to get a better understanding of how to make an Access system available for multiple clients. Here is some background:
* We have nearly completed developing an Access system
* It was originally intended for one user (our local yacht club)
* Other clubs may be interested
* Rather than redevelop as an Access Web App we are inclined to set up a Terminal server environment and give access to users via RDP, Coord etc (that way we can use desktop Access over the net and continue to use VBA programs, reports etc)

What I am interested in is how to best to set the system up for use by multiple clubs. Thoughts on this include:
* if we set up a copy of the database for each club separation of club data is simple and robust but we would be faced with updating multiple systems for any changes etc. If the system became popular this could be a big task
* we could possibly use a single system with client data partitioned so that each club can only see their own data. I am not sure how difficult this would be and how robust in practice
* is there another way to do this with say common forms and queries but different data sets?

Thoughts and ideas from the more experienced would be much appreciated

Thanks in advance
Solar Paul

 

[gemma-the-husky]

i think you would be better with 2 alternatives

1. develop this to run as a web app

2. develop as a standalone system to sell/distribute

I cannot think you would want multiple "strangers" logging in to your PCs to run apps. Besides security issues, there would be a complex/expensive licensing issue.

 

[Solar.Paul]

Hi Dave

Thanks for your response. I have comments about the alternatives you raise as follows:

1 Access Web apps don't support reports - I presume they will at some stage but I don't know when

2 My colleague who has undertaken to write several VBA programs for key functional areas thinks that macros in the Webb App can't do as much/aren't as procedurally sound as VBA. He acknowledges that this is a preconception and is currently investigating whether this is the case. We are very keen to hear the views of experienced builders of Access Web Apps

3 I consider that web applications/ working in the cloud is very much the way of the future and I don't want to market a product for downloading onto a local computer. I very much want the data to be accessible and shared by all users from every computer/tablet/smartphone

4 I note your concern about security and licensing issues:
I have set up a terminal server environment before and am confident that robust and secure virtual PCs can be set up which limit users access to their Access database only and for a couple of dollars per user per month (using AADS Worldwide which I have used before and heartily recommend). I will check with Microsoft re licensing of Access but expect that it will be ok to use Office 365 small business which costs around $A 16.50 per user per month here in Australia and is a reasonable amount

So I think that this comes back to the issue of the best way to set up Access so that users only see data without having to update every client copy manually for every update. Any thoughts on this?

Thanks
Solar Paul

 

[gemma-the-husky]

well in that case, if the users do not know one another, then personally, I think you should keep the data-sets separate.