a2k getting multi-user right from the off

[Deano]

Hi,

I feel I have a good learning opportunity here. I have been asked to
knock up a simple db for managing lettings of rooms and halls. I'm
confident about the design but want to make it multi-user even though
it's not strictly necessary right now.

I've not much experience in this even though i've read the correct
websites that have been listed here many times, down to tips about not
using domain aggregrate functions to improve performance (admittedly
that confuses me as I don't see how I could get by without them, but I
digress).

I do have three questions, one general related to the above and two
specific,

First, if you do want to develop a simple multi-user database, what
basic tips would anyone give? I reckon this one will use optimistic
locking and won't be used by more than 10 people at a time, and
probably just 2 in most cases.
What things could I design into (and out of) my app that will save me
grief later on?

Secondly, if I'm distributing a runtime only version and have split
into front and back-ends, how do the users (who don't have Access)
control security? I presume I have to design a form and use VBA to
allow them access to users and passwords? In this scenario I guess the
workgroup security file would be on the server with the tables?

Finally what tips are there for testing on networks? Does working on a
domain vs p2p model make any difference in how Access works?
thanks
Deano (multi-user noobie)

[Deano]

Albert D. Kallal wrote:

"Deano" <ma**********@g mail.com> wrote in message
news:xn******** *******@usenet. plus.net...

"...if I'm distributing a runtime only version and have split into
front and back-ends, how do the users (who don't have Access)
control security?

Yes...that is correct. However, with a good design, then likely this
process can be simplified a lot (low, medium, and super users for
example).

I presume I have to design a form and use VBA to allow them
access to users and passwords?

Yes, that is generally what you do. I actually prefer this, even when
NOT using the runtime. I give some example screen shots of this idea
here

http://www.members.shaw.ca/AlbertKal...ity/UserFriend
ly.htm

In this scenario I guess the workgroup
security file would be on the server with the tables?"

Yes, that is correct....

Thanks Albert, it's useful to have these basic questions answered.
Site's looking nice as well.