If you want to place a password on the data base, you can only do that in inclusive mode

@ Sami, I get that, but why is there such an opening that isn't "exclusive" on a non-split database?

I see what you are saying. Here is a scenario.

You should not do this, but it is permissible:

Non split database on the server, programmer 1 login and works on Form1, programmer 2 login and works on Report2.
They can't do that if the DB is open in exclusive.

@ Sami Exactly my point, why allow something that shouldn't be done? Huh?
Or maybe it's better to ask, under what situations would there be "corruption" if two users/programmers get into the same db file at the same time? How would we know some corruption has happened?

I think you would know pretty quick once the corruption occured. The corruption could present with various symptoms but the one that I've experienced a few times now was I accidentally corrupted myself a few times with currentdb.execute statements and trying to be clever with creating new records/deleting records/editing records while currently editing a record all at one go kind of thing without thoroughly planning through the code, this is basically the same thing that could happen with 2 users interacting at once, in my case it was myself and my code lol. Half of the fields in my table would change to #Deleted and you could not change that field again ever from #Deleted, if you tried to it would tell you that someone else is currently making changes to the field. (It's not the record is deleted, it's a single value in a record, like FirstName for instance, but you can still interact and change all the other fields in the record fine)