Split or Share

[Guest]

I have a database which only 4 or 5 users need to use. What is the better
option: share the database or split it? Is one way better than the other
under certain circumstances.

Thanks

 

[Guest]

Whenb more than one user is going to connect to a database it is better to
split. Put the tables on the server and the forms, reports... on each PC

 

[Douglas J. Steele]

Even with single user databases, I still always split. That way, you can
make changes to the application without having to worry about their existing
data.

 

[Guest]

Many thanks, in other words, forget sharing!!

Even with single user databases, I still always split. That way, you can
make changes to the application without having to worry about their existing
data.

 

[David W. Fenton]

I have a database which only 4 or 5 users need to use. What is the
better option: share the database or split it? Is one way better
than the other under certain circumstances.

There are no options.

SPLIT.

ALWAYS.

 

[Guest]

Now that I've split the database, I've got the BE on the server and have the
FE copies on two machines. I've re-linked the tables, but when I go into
either of the FE I cannot create any new data. What else do I now have to do?

Thanks

 

[Douglas J. Steele]

Each user must have Change permission (at least Read, Write, eXecute and
Delete) on the folder where the back-end file exists.

 

[aaron.kempf]

you don't need to split; these guys are full of hot air

you do need to use Access Data Projects to support that many users
with MS Access

 

[Guest]

Many thanks

Each user must have Change permission (at least Read, Write, eXecute and
Delete) on the folder where the back-end file exists.

 

[David W. Fenton]

Each user must have Change permission (at least Read, Write,
eXecute and Delete) on the folder where the back-end file exists.

Delete is not necessary.

 

[Douglas J. Steele]

Delete is not necessary.

You're right that it's not absolutely necessary, but if they don't have it,
it can impact the ability to do compacts (since the ldb file won't get
deleted when the last user disconnects)

 

[David W. Fenton]

You're right that it's not absolutely necessary, but if they don't
have it, it can impact the ability to do compacts (since the ldb
file won't get deleted when the last user disconnects)

Why would anyone other than an administrator be doing compacts? All
you have to do is give regular users MODIFY permossion and your
administrators CHANGE permission (i.e., with DELETE).