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

Access in a workgroup?

P: n/a
After some basic research, I am still somewhat unclear on how Access would
be used in a workgroup setting. Basically, we want to run 10 MS Access
clients to access an MS Access database on a standalone PC running Windows
XP Pro. Do we need SQL server or some other application running on this
"server"?

We need to have

1) multiple people accessing the database simultaneous (should be no
concerns about who saves first)
2) Administrator capabilities to control different levels of permissions
3) We don't want to run any form of terminal service, Citrix, or an form of
application sharing. We want to use the resident Access clients on each
user's machine.

Oddly, Microsoft was unable to answer basic questions about using MS Access
in a workgroup format? Isn't this an EXTREMELY BASIC requirement?


Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
ajdfljsdf <as****@sss.com> wrote:
: After some basic research, I am still somewhat unclear on how Access
: would be used in a workgroup setting. Basically, we want to run 10
: MS Access clients to access an MS Access database on a standalone PC
: running Windows XP Pro. Do we need SQL server or some other
: application running on this "server"?

This is not a problem. I have several split Access databases with that
many users on a WAN, with the program files on the resource servers that
are local to each user, and the data files on the closest resource
server to the majority of user.

:
: We need to have
:
: 1) multiple people accessing the database simultaneous (should be no
: concerns about who saves first)
: 2) Administrator capabilities to control different levels of
: permissions 3) We don't want to run any form of terminal service,
: Citrix, or an form of application sharing. We want to use the
: resident Access clients on each user's machine.

Access' .mdw security works fine for different levels of permissions,
and shared use of the files is easy to arrange.

: Oddly, Microsoft was unable to answer basic questions about using MS
: Access in a workgroup format? Isn't this an EXTREMELY BASIC
: requirement?

--

Please remove the under_scores if sending me mail.

Nov 12 '05 #2

P: n/a
"ajdfljsdf" wrote
. . . how Access would be used in a workgroup
. . . 10 MS Access clients


You'll find a downloadable presentation that I did for my user group at
http://appdevissues.tripod.com/downloads.htm. Then, you'll find the best
collection that I know about of information and hyperlinks on the subject at
MVP Tony Toews' site http://www.granite.ab.ca/accsmstr.htm.

There's no scarcity of information on the subject -- it's called "mulituser"
and you'll find a lot of threads in the archives of comp.databases.ms-access
at http://groups.google.com. Oh, yes, there is a separate sponsored
newsgroup on this subject microsoft.public.access.multiuser.

I suspect it's just a matter of knowing the appropriate word to use to find
the information.

Larry Linson
Microsoft Access MVP
Nov 12 '05 #3

P: n/a
"ajdfljsdf" <as****@sss.com> wrote:
1) multiple people accessing the database simultaneous (should be no
concerns about who saves first)
2) Administrator capabilities to control different levels of permissions
3) We don't want to run any form of terminal service, Citrix, or an form of
application sharing. We want to use the resident Access clients on each
user's machine.

Oddly, Microsoft was unable to answer basic questions about using MS Access
in a workgroup format? Isn't this an EXTREMELY BASIC requirement?


To add to other postings. Multi user capability is available right out of the box.

There are some basics you should do such as splitting it but otherwise not a problem.
You want to split the MDB into a front end containing the queries, forms, reports,
macros and modules with just the tables and relationships. The FE is copied to each
network users computer. The FE MDB is linked to the tables in the back end MDB
which resides on a server. You make updates to the FE MDB and distribute them to
the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page at my website
for more info. See the Auto FE Updater downloads page at my website to make this
relatively painless.. It also supports Terminal Server/Citrix quite nicely.

Mind you #2 with respect to administration probably requires Access security which
can be some work. Standard blurb follows.

ACC: Microsoft Access Security FAQ Available in Download Center
http://support.microsoft.com/support.../q165/0/09.asp
It is suggested you reread this FAQ several times. I must admit I never quite
understood it.
ACC: Overview of How to Secure a Microsoft Access Database (A2.0 to A97)
http://support.microsoft.com/support.../q132/1/43.asp
ACC2000: Overview of How to Secure a Microsoft Access Database
http://support.microsoft.com/support.../Q254/3/72.ASP
ACC2002: Overview of How to Secure a Microsoft Access DB
http://support.microsoft.com/support.../Q289/8/85.ASP

Note however there have been isolated postings indicating security has been cracked.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.