By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,790 Members | 1,407 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,790 IT Pros & Developers. It's quick & easy.

a2k Turning a single-user app into a multi-user app

P: n/a
One of the more challenging things on my app's wishlist is to make it
multi-user on a LAN.

For the record my app was always intended to a single-user but things have
changed. It's mostly composed of bound forms handling records numbered in
the hundreds, sometimes a few thousand. The code of course refers to tables
in the local mdb.
I allow the user to create external backups of the tables in the database
and to restore them. Because of this feature there is no workgroup security
as I have to allow enough permissions for these backup/restore tasks to
work.

After opening the app I allow different users to be created to access
different areas - this also restricts the tables they can backup or restore.

In a network scenario I guess I would need to split the database and put the
tables on a server.
I would like any user to be able to log on from any workstation and use the
app according to their level of access.
I would stop the existing backup/restore functions obviously but how would I
backup the tables on the server? (Creating an external mdb with backed up
tables is quite useful to us).
The tough part would be rewriting the code to refer to the server,
implementing locking etc.

I'm wondering whether to implement workgroup security given that the tables
will be on the server and the front-end will be a locked down MDE using the
Access Runtime. It's more important that I can have user accounts that
allow different areas of the app to be accessed. I *think* I could do this
with Access security - i.e determine the user who's logged on then allow
certain buttons on the form to work - is that the best way given that I want
users to be able to roam?

So would anyone be able to offer some general advice and perhaps a
recommended series of steps that one should take when embarking on this
task? (or a web link if there is one).

Apologies for the verbosity!
cheers
Martin
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Take a look at Tony Toews web page: http://www.granite.ab.ca/accsmstr.htm

Specifically look at : http://www.granite.ab.ca/access/splitapp/index.htm
for information on splitting your application to FE(front end) and BE(back
end), and using Access in a multiuser configuration.

Tony also has some links to other places that will be helpful.

If you don't have it, purchase the AccessXX Developer's Handbook by (where
XX=version). If your version is 2000 or above, there are two volumes. The
second volume contains tons of info
regarding Access as Client/Server or over a Lan.

Look at this newgroup: microsoft.public.access.multiuser for a lot of good
info.

Do a google search on THIS ng for "multiuser".

HTH
Ruben Baumann
"Deano" <de*********@hotmail.com> wrote in message
news:41*********************@ptn-nntp-reader02.plus.net...
One of the more challenging things on my app's wishlist is to make it
multi-user on a LAN.

For the record my app was always intended to a single-user but things have
changed. It's mostly composed of bound forms handling records numbered in
the hundreds, sometimes a few thousand. The code of course refers to tables in the local mdb.
I allow the user to create external backups of the tables in the database
and to restore them. Because of this feature there is no workgroup security as I have to allow enough permissions for these backup/restore tasks to
work.

After opening the app I allow different users to be created to access
different areas - this also restricts the tables they can backup or restore.
In a network scenario I guess I would need to split the database and put the tables on a server.
I would like any user to be able to log on from any workstation and use the app according to their level of access.
I would stop the existing backup/restore functions obviously but how would I backup the tables on the server? (Creating an external mdb with backed up
tables is quite useful to us).
The tough part would be rewriting the code to refer to the server,
implementing locking etc.

I'm wondering whether to implement workgroup security given that the tables will be on the server and the front-end will be a locked down MDE using the Access Runtime. It's more important that I can have user accounts that
allow different areas of the app to be accessed. I *think* I could do this
with Access security - i.e determine the user who's logged on then allow
certain buttons on the form to work - is that the best way given that I want users to be able to roam?

So would anyone be able to offer some general advice and perhaps a
recommended series of steps that one should take when embarking on this
task? (or a web link if there is one).

Apologies for the verbosity!
cheers
Martin

Nov 13 '05 #2

P: n/a
R Baumann wrote:
Take a look at Tony Toews web page:
http://www.granite.ab.ca/accsmstr.htm

Specifically look at :
http://www.granite.ab.ca/access/splitapp/index.htm for information on
splitting your application to FE(front end) and BE(back end), and
using Access in a multiuser configuration.

Tony also has some links to other places that will be helpful.

If you don't have it, purchase the AccessXX Developer's Handbook by
(where XX=version). If your version is 2000 or above, there are two
volumes. The second volume contains tons of info
regarding Access as Client/Server or over a Lan.

Look at this newgroup: microsoft.public.access.multiuser for a lot of
good info.

Do a google search on THIS ng for "multiuser".

HTH
Ruben Baumann


cheers thanks for the tips.

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.