New in this version of SharePoint (WSS or MOSS) is the ability to force checkout of files before editing can occur. This solves the
previous problem of:
1. User A opens a file without checking it out
2. User B Checks out a file
3. user B Checks the file back in
4. User A hits the 'Save' button
Now, even though user B was was the only user that checked out the file, User A's file is the last version. To prevent
this, enable forced checkout from Document Library Settings, General Settings, Versioning Settings, and Check Yes 'Require documents to be checked out before they can be edited?'
The unexpected behavior (or maybe planned behavior) occurs when you enable forced checkout. When a user uploads files via Webdav,
that is via the Explorer View or Multiple File Uploads, the files are automatically in a checked-out state. On one hand, this is
great because the file isn't usable until the user checks it in. This allows for the collection of forced metadata on checkin. The
downside, however, is that the files aren't viewable by anyone, INCLUDING the Site Collection ADMINISTRATOR, until they are checked in.
So, a user could theoretically upload large volumes of content to a Site Collection, completely consuming the quota and there is no way,
as far as I can find at this point, to find them.
A user can upload items to a list that nobody can see! (except that user)
Ben Curry
Mindsharp