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.

I work in a very real state government agency. My colleagues are using it
to manage their projects, and I'll list (hey - you asked if it was real)
just a few of the features that make it more than a card filing system:

* Every night my VBA code runs 42 queries that append and update data in our
application from an Oracle database, SQL Server and another Access database.
They also upload different data to that other Access database.
* In addition to projects, it also manages leases, contacts, activity nd
documents.
* It uses the OS login name to distinguish between editable and read only
records, depending on whether the user is a team member of the project
* there are 5 user classes - user, admin, admin User, read only and a 5th
one that I can't recall at the moment - and depending on which class the
user belongs, different forms and different form controls will be presented
to the user.
* It's also a document processing file manager. My users process lots of
contracts and documents, and my application enables them to select from
hundreds of documents in Word, Excel, PDF and html from a shortcut menu
sysem, and it populates fields in the documents with data in the database.
It also saves the files into the project folder on the network drive, so the
user doesn't have to navigate through Windows explorer to find the project
folder.

We have conservatively estimated that the file management module I just
described is saving our agency and the taxpayer the time equivalent of over
$500,000 per year.

Maybe you don't have a problem because you designed your database better
than I did. I do have memo fields in two tables, and Tom Wickerath has
pointed out that could be the problem.

But yes, it's a real database, and I'm dealing with a very real problem.

Paul