Multi-User Application

Hi everybody,

my company has an issue and I have to solve it. I have to create a
multiple users application, its basically a form that stores data on
just one database table.
To make it faster i wanted to use MS Access because they need it really
fast.
How do I enable Access 2003 to multiple user?

Thanks for any help.

re: Multi-User Application

gabry.morelli@libero.it wrote:I have created a multi user application in the past.

I guess you can enable the user and group features of the database but
as I vaguely remember now, I didn't go with this solution. Access is
not robust when it comes to this feature.

A simpler approach might be to just maintain your users in a separate
table and and then authenticate thru the application itself. Also you
might consider a lock table (which is what I used) which ensures that
only user is writing to the table at one time. Enterprise level
databases do all these things for you. But then they are very
expensive.

- VV

re: Multi-User Application

gabry.morelli@libero.it wrote:
Give everyone that needs it a copy of Access or else an access runtime
of the database. You can split the database and put the backend on the
network and give the users the front end.

re: Multi-User Application

On 8 Sep 2006 07:18:35 -0700, gabry.morelli@libero.it wrote:

Access is multi-user out of the box.
Put your table in an MDB. This will be the back-end database. Put it
on a file server.
Put all other objects (queries, forms, etc.) in a second MDB. Add a
link to the table in the back-end (File Get External Data Link
Tables). Put it on each user's machine.

-Tom.

re: Multi-User Application

Thank you so much Tom, this seems to be a very good solution.

But is there any problem if two users access simultaneously the same
table?


Tom van Stiphout ha scritto:

re: Multi-User Application

<gabry.morelli@libero.itschreef in bericht news:1157726924.377210.74680@h48g2000cwc.googlegro ups.com...There *might* be some problems like writeconflicts when the same table is used at the same moment.
It depends on how many simultaneous users there are and what they are 'doing' in the database...

I assume this is mainly input of data ?
You could use a local temptable in each users frontend that can be stuffed and edited by each user.
Validate the input and let them hit a Save-button.
'Save' saves the data in the real backend-table (appendquery) and clears the records in the temptable (deletequery).
I bet you will hardly ever (in fact I think never) have a writeconflict that way.

Arno R

re: Multi-User Application

On 8 Sep 2006 07:48:44 -0700, gabry.morelli@libero.it wrote:

Not really, just try it.
Reading from the same table at the same time is not a problem. Writing
is, but two (or even 10) users rarely write at the exact same
millisecond.

Arno is right about his possible work around, but I would not go there
unless forced by too many write conflicts.

-Tom.