Multi user environment

[chaft]

Ok I'm trying to get my head into gear for the final phase of my small project. I split the database into forms and tables.
Have put the table file on the sever and given everyone their local copies of the forms.

I tested it the other and I was pretty happy except for two things.

1) when deleting at the same time I get #DELETED records in the forms which disappear when I Requery the record

2) I did get an dialogue box that told me someone had made changes and whether I wanted to discard or keep the record.


Ideally if the #deleted problem is solved by simply requerying the form then I'm happy to set up the code.

Probably form.requery I guess.

However for the second problem Should I start putting locks on things such as suggested in:

http://www.tek-tips.com/faqs.cfm?&rat1=2&fid=3571

Other than that should I be considering any other things to be sure of an easy record keeping experience? Like whether I should have specific logins for users or something.

This is a small scale project, 5 Data enterers at max.

I am intrigued to hear your responses or comments?

 

[JoeAtWork]

In most of my applications people don't delete things very often, nor do they update the same record very often. So I just let Access's built-in messages handle the rare occasion these pop up.

Quite frankly if I expected a lot of record contention between users I would do everything possible to avoid writing the application in Access. Trying to bypass Access's built-in mechanisms for handling multi-user conflicts can be quite cumbersome, and negate the main reason to use Access in the first place (ease of use).

Regarding your questions about logins, that is really determined by your requirements. Generally I find there are two reasons to implement logins:
1. If you prefer to allow one group of users to be able to do and see more things than others
2. If you would to set up some sort of audit logging, i.e. record who did what