I'm afraid your problem will be, that when user opens Excel workbook, and makes any changes in it, the Excel this user is working with is a copy of workbook in memory of user's computer (or e.g. in memory of some Terminal Server). The changes are saved to real workbook only when the workbook is saved. And any VBA code is running in memory in system and instance, the this particular user is working from.

And when several users are trying to force the save their own instances of same workbook practically at same time ...

I understand your concern regarding simultaneous edits in Excel workbooks. You're right that each user works on a local copy in memory, and changes are only saved to the original file when the user explicitly saves it. This can lead to conflicts when multiple users are trying to save their changes at the same time.

Since only a few members will be actively editing the Excel workbook while the majority will just be reading it, the situation should be more manageable.

Do you have any samples or ideas on how to achieve that?