Preventing Corruption in Multi-user environment

[swampg8r]

I'm in the process of rolling out a new database that will require some data entry from approximately 35 users.

I have been told that database corruption WILL (not might) occur if more than one user is in the database at a time, which I find hard to believe. I was told that if multiple users who have different permissions levels are in the DB at the same time, this will cause corruption.

Has anyone heard anything like this?

Also, there will only be one or two forms that my users will be using for data entry. The rest is report running. If I set the value Record Locks on the form to EDITED RECORD, will this prevent corruption?

Any input you could provide is very much appreciated. I haven't been able to find any info specific to this issue.

 

[ScottGem]

I will not say that corruption will definitely occur, but its not unlikely with a multi-user database that is deployed incorrectly.

ANY multi-user database NEEDS to be split between Back End (tables) and Front End (everything else). The Back end is located on a network server or shared drive. For optimal performance and stability the Front End is located on the local PC.

Using such a deployment strategy will minimize any chance of corruption.