What should i consider when building a multi-user db?

[ant1983]

Hey Guyz,

Was just wondering...

I plan to build a db in a multi user enviroment. I'm a complete novice so
was just wondering what i should be considering?

There will be about 5 users using the interface, writing to the same tables
and looking up stuff from the same tables...

I was thinking of saving it to one of the pc's and just sharing it but first
need to know if this is a good or bad thing.

The alternative (although its probably not an alternative as it comes down
to the same thing) is to save it on the servers and give all 5 users
shortcuts to it. (Prob onluy benefit here is that it will be backed up?)

Anywayz... Eveyones comments would be highly appreciated !!!

Cheers!

Wayne

 

[John W. Vinson]

Hey Guyz,

Was just wondering...

I plan to build a db in a multi user enviroment. I'm a complete novice so
was just wondering what i should be considering?

There will be about 5 users using the interface, writing to the same tables
and looking up stuff from the same tables...

I was thinking of saving it to one of the pc's and just sharing it but first
need to know if this is a good or bad thing.

The alternative (although its probably not an alternative as it comes down
to the same thing) is to save it on the servers and give all 5 users
shortcuts to it. (Prob onluy benefit here is that it will be backed up?)

A hybrid of these two approaches is universally recommended. You can "split"
the database into a "Backend" containing tables (and only the tables), and a
"frontend" with links to the backend tables, and all of the queries, forms,
reports and code. See
http://www.granite.ab.ca/access/splitapp.htm
for a detailed discussion of this technique.

A single shared database is a *bad* idea; if one user has anything open in
design mode, nobody else can even get in, and you'll get bloating, slow
performance, and a higher risk of corruption.

John W. Vinson [MVP]