VBA project does not close when workbook is closed

[SimonN]

I have a large project that uses VBA to open and close files. The project is
password protected. I recently ran into a problem whereby a password prompt
appears when closing Excel and VBA projects remain open after the
corresponding workbooks have been closed.

This error was apparently caused by omitting statements in the style of 'Set
objectName to Nothing' before closing the workbook (a solution documented in
other forums). This has since been corrected. The password prompts no
longer appear and workbooks are closed by the code without problems.

However, the problem I now have is that VBA projects now remain open for any
spreadsheet that is manually opened and closed (regardless of whether they
have any code in them). Re-opening the same file causes a second instance of
the same project to appear. They remain open until Excel is shut down.

I have tried cleaning my code and re-installed Excel but have been unable to
find a fix. I have found references to other people seeing similar symptoms,
but no solutions. My suspicion is that there may be some sort of hangover
issue in the registry or with DLLs, as all workbooks are affected.

I am using Excel 2002 with SP3 (although identical symptoms have been seen
on a colleague's machine which runs Excel 2003).

Any assistance would be greatly appreciated.

Simon.

 

[MarkRob]

Simin, I have the same problem. All I have done is open another VBA project
which opens a form. When exiting, I get the password prompt problem. How
did you get rid of it. What objects need to be set to nothing?

regards
mark

 

[SimonN]

Mark,

Turns out the problem was specific to my development box - apparently
something goes wrong with Excel at some point (but no idea what or when!).
When I tried the same code on a different machine (with same version of
Office, Excel etc) it worked OK.

Hence I've rebuilt my development machine. Excel was already playing up as
projects always remained open after the associated workbook was closed (even
if they did not contain any VB!). Sadly he only way I have found to get rid
of this in the past has been a complete reformat and rebuild. Even
reinstalling Office did not cure it.

Not a very satisfactory solution I'm afraid.

Cheers
Simon.

 

[markww]

It appears Google desktop is the culprit. I have removed it and m
problems have gone away. Did you have Google desktop on your proble
machine?
regards
Mar

 

[deanl144]

Thanks alot for pointing me to the Google Search tool, I spent hours
last night trying to figure out what was going on.