VBA Password box appearing at close
 

I have a workbook which contains macros. Just recently when I close the
workbook the vba editor password box has started to appear after excel has
shut down. The vba editor was never opened!
I can either supply the password and click "Ok", or I can click cancel twice
without supplying the password, and it disappears.
Any ideas why this has started happening - I have not changed any code, to
cause this.

Thanks
Sandy

VBA Password box appearing at close
 

This used to be a common complaint for people who were using Google's desktop
search.

Any chance you're using that program?

or...

Did you start to record a macro and then decide not to (a long shot!)?

Sandy wrote:

I have a workbook which contains macros. Just recently when I close the
workbook the vba editor password box has started to appear after excel has
shut down. The vba editor was never opened!
I can either supply the password and click "Ok", or I can click cancel twice
without supplying the password, and it disappears.
Any ideas why this has started happening - I have not changed any code, to
cause this.

Thanks
Sandy

--

Dave Peterson

VBA Password box appearing at close
 

Should have mentioned Excel 2003 - does not happen with a converted book in
2007.
Sandy

"Sandy" wrote in message
...
I have a workbook which contains macros. Just recently when I close the
workbook the vba editor password box has started to appear after excel has
shut down. The vba editor was never opened!
I can either supply the password and click "Ok", or I can click cancel
twice without supplying the password, and it disappears.
Any ideas why this has started happening - I have not changed any code, to
cause this.

Thanks
Sandy

VBA Password box appearing at close
 

Hi Dave
I don't use Google's Desktop Search Dave and I haven't got any half recorded
macros either - BUT - I had dabbled with "Microsoft Office Live Add-in"
toolbar.
I have just uninstalled it and the problem has disappeared.
Don't know why it should have caused this but....... seems to be the
culprit!!
Sandy

"Dave Peterson" wrote in message
...
This used to be a common complaint for people who were using Google's
desktop
search.

Any chance you're using that program?

or...

Did you start to record a macro and then decide not to (a long shot!)?

Sandy wrote:

I have a workbook which contains macros. Just recently when I close the
workbook the vba editor password box has started to appear after excel
has
shut down. The vba editor was never opened!
I can either supply the password and click "Ok", or I can click cancel
twice
without supplying the password, and it disappears.
Any ideas why this has started happening - I have not changed any code,
to
cause this.

Thanks
Sandy

--

Dave Peterson

VBA Password box appearing at close
 

If I recall correctly, the problem with the google desktop search (maybe fixed
now????) was that it tried to get into the VBE to examine and index the code in
the workbook's project.

Maybe that MS Office Live addin is doing a similar thing????

I don't recall anyone complaining about that addin, though. But maybe it's more
of a comment on how often it's used <vbg.

Sandy wrote:

Hi Dave
I don't use Google's Desktop Search Dave and I haven't got any half recorded
macros either - BUT - I had dabbled with "Microsoft Office Live Add-in"
toolbar.
I have just uninstalled it and the problem has disappeared.
Don't know why it should have caused this but....... seems to be the
culprit!!
Sandy

"Dave Peterson" wrote in message
...
This used to be a common complaint for people who were using Google's
desktop
search.

Any chance you're using that program?

or...

Did you start to record a macro and then decide not to (a long shot!)?

Sandy wrote:

I have a workbook which contains macros. Just recently when I close the
workbook the vba editor password box has started to appear after excel
has
shut down. The vba editor was never opened!
I can either supply the password and click "Ok", or I can click cancel
twice
without supplying the password, and it disappears.
Any ideas why this has started happening - I have not changed any code,
to
cause this.

Thanks
Sandy

--

Dave Peterson

--

Dave Peterson