Here's a funny one. Seems fundamentally 'expected behaviour' to me, but anyway..
Chappy opens up an Excel workbook. The workbook is flagged that it should be opened up read-only unless vital not to. So the chap clicks "Open as Read-Only" as recommended.
He then opens up the same workbook again, but as Read/Write. The idea is that he can refer to the original one whilst working on the editing in-progess one.
I'm not 100% why he wants to work this way, but he wants to.
The problem is that in opening the workbook for a second time as Read/Write, the initially opened workbook loses its read-only status, meaning he can accidentally save the original over his work in progress.
I tried googling, but it's a tough one to pin down with search terms.
The worksheet is held on a Windows Server, so CIFS/SMB share, in an Active Directory environment. XP Pro client.
I'd guess and say it's pretty expected behaviour and could at worst be called a limitation in either Excel's or NT's file locking. More likely the former (Excel's method of flagging something as RO/RW, rather than NT's which I'm sure would flag each occurrence with a session ID or something).
Anyone ran into this before? It's not something I've had cause to look into before. My feelings are that he should not work this way, and should make a copy of the file and work on that.