I have a front end/backend database with multiple users working at the same time. The database often is corrupted and displays what appears to be chinese characters. If I attempt to delete the record containing these characters, I get the message "Search Key not found in any record". I cannot remove the record even after compacting and repairing the database. The only way to fix the problem is to import the tables into a new database. Only then am I able to successfully remove the record.
I have been unable to determine what triggers the creation of the characters.
If you have multiple users, each one should have a dedicated front-end. All sorts of problems arise if startup scripts (or just clicking on the front-end .mdb file) all point to the one copy. For instance, I have a client who is a function caterer and each user has an icon on their desktop which calls up a different copy of the front-end, eg. caterDB1.mdb, caterDB2.mdb and so on. Of course, they are all linked to the same back-end. This methodology also asserts concurrency privileges, i.e. only the first user to open a record can modify it.
In addition, each of these front-end copies maps onto a corresponding directory where extracted data (excel, mail-merge etc.) is stored to avoid any possible overwriting. I have not noticed any limitation on user numbers with this scenario (max I have seen is about 25).
The front end applications are all stand alone with each pointing to the same back end database. Basically, it is a tracking board of patients. The users view a page of continuous forms displaying about 20 records. A user can click on any one of the records to open up a more detailed page where changed can be made. I have "edited records" for the record locks property.
I have tried that method Jim and the only way 25 users would NOT damage the sole access back end file is if they were mostly read only users or those making very infrequent changes. If you have 25 users HAMMERING the application, that configuration would have major corruption issues and the back end would have to be compacted and repaired on an daily basis.