Paul wrote:
No, this is a real issue for me. I've spent the last year working on a very
real project management database in Access 2003. At the moment, I have 40
users, and a week from Monday, I'm going to have about 100. Just within the
past three weeks, my users have started to encounter the Write Conflict
error I described in my first post.

Other posters has given you many excellent advices. I just want to rule
out one more cause of write conflict: It is possible that the write
conflict errors are bogus because of VBA coding stepping on itself or on
the Access. A good way to do this is to have VBA execute a separate
query that modifies the same record that is being edited in the form.
This comes out as two separate connection and of course the software
(whether it's Access or the backend RDBMS) has no idea that the two
separate connection are actually the same application/user and perceive
it as deadlock for this reason.

Therefore, if your VBA code behind the forms does use queries that
update the same record or maybe different record on the same table that
could be on the same page, this will cause write conflicts.

If your code doesn't have that, then you're probably good and want to
look at others' excellent solutions.

Best of luck.