I worked years in a development and production environment, so I understand that users get a final version. The development version is, well, the development version.
1. in Document_Open VBA does NOT, repeat NOT, take control of the User's options. VBA does only what you (as the developer) tells it to do, in the code in Document_Open. No more, No less. If you do not write code into the Sub Document_Open, then nothing happens. It only does what you tell it to do.

2. "and does not allow the User the option of entering the VB Editor".
a) well sort of, in that while the code is executing, no, there is no access to the VBE, but only a the fact you can not start it.
b) why why why on earth do you want users to access the VBE anyway!!!!???

Quote:

then there is no easy way for the Developer to access the VBE by simply opening the document

There is a very easy way, once Document_Open finishes, open the VBE. This has nothing to do with whether the Open instruction came from double click or RMC-Open.

Yes of course users have a "closed" version - and therefore why are they going into the VBE. Yes of course developers have an "open" version for further development. In which case, as long as nothing is actually executing, they have full access to the VBE.