VBA Module Editor

[Guest]

Enviornment: MS Access 2002 (XP) and VSS 6.0d

Is there a way to clear the list of modules that the VBA editor
'automatically' opens? What's happening is when I go to open a module and
answer yes to checking it out of VSS, it then asks to check out a bunch of
other modules that I worked on in the past. What ends up happening is that
I've got to go through the process twice in order to get the code window open
with the module that I want to work on. I've tried closing all modules
before closing the VBA editor window, but that does not help. At this point
I wished that it didn't remember any of the previously opened modules.

Thanks.

 

[Brendan Reynolds]

Try forcing a save. Make some change, for example comment then uncomment a
line, or put in a blank line then take it out again. Then close all modules
(or all except those that you want to open next time you open the VBE) and
save before closing the VBE.

 

[Dirk Goldgar]

Enviornment: MS Access 2002 (XP) and VSS 6.0d

Is there a way to clear the list of modules that the VBA editor
'automatically' opens? What's happening is when I go to open a module
and answer yes to checking it out of VSS, it then asks to check out a
bunch of other modules that I worked on in the past. What ends up
happening is that I've got to go through the process twice in order
to get the code window open with the module that I want to work on.
I've tried closing all modules before closing the VBA editor window,
but that does not help. At this point I wished that it didn't
remember any of the previously opened modules.

I don't know whether the use of VSS makes a difference to this solution
or not, since I don't use it, but what I find (without VSS in the mix)
is that I need to make a change to some module or other -- even a
trivial change -- then close all the modules, and then click the Save
button on the VB Editor's toolbar. That seems to save not only the
module I changed, but also the state of the editor and its windows.
Have you tried that?

 

[Guest]

Thanks that does work.

I don't know whether the use of VSS makes a difference to this solution
or not, since I don't use it, but what I find (without VSS in the mix)
is that I need to make a change to some module or other -- even a
trivial change -- then close all the modules, and then click the Save
button on the VB Editor's toolbar. That seems to save not only the
module I changed, but also the state of the editor and its windows.
Have you tried that?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)