Thank you for your quick reply, Doug. I really appreciate it!

I'll do a quick test to see what error is returned if the file is already open. I agree that there *should* be some sort of lock, but I haven't found any documentation along those lines.

I'm not a DB person by any stretch, which is why I didn't implement one in the first place, plus the fact that the site is not critical in any sense of the word - it's for a club. But, I think a DB would solve the problem because each user would have their own DB record, so userA and userB saving at the same time would impact 2 different DB records. I'm not going to worry about userA having two different sessions and simultaneously hitting save!

Maybe I'll dive into creating a DB as my next enhancement. :)

Thanks again,

Jeff