Project - VBA Project window - Excel 2003

[Jarek Kujawa]

Hi,

1. I open a file, write some code, then close the file

2. even though the file was closed it's code is still viewable in
Project - VBA Project window, as if the file was still open

the only way I know to have the file REALLY closed in Project - VBA
Project window is to Exit and re-start Excel

does anyone know a better way?

TIA

 

[Patrick Molloy]

the code modules are part of the workbook, so if you close the workbook, you
close the project. Have you written the code in the Personal.xls or somewhere
other that the workbook you thought?

 

[Jarek Kujawa]

nope - I don't use personal.xls


ANY file behaves the way I described.

I close the file, it is closed BUT the project stays open.
I close all the files that were open and ALL of their VBA projects
remain open as if the files were still open

by double-clicking on the projects I can see all the code of any of
the files that were open

 

[Jarek Kujawa]

thks Simon

1. "Method 'VBProject' of object '_Workbook' failed" is what I'm
getting

2. am afraid this does not do what I am looking for - if I open/close
the same file several times I can see 'all' (the same) several
VBPRojects in VBE window

 

[Jarek Kujawa]

should I do that for any file?

cause I did that for several of them and to no avail

after restarting Excel and re-opening the files the library was not
added

 

[Jarek Kujawa]

thks

but not always

apparently

so if you close the workbook, you
close the project










- Pokaż cytowany tekst -

 

[Chip Pearson]

I''ve seen that from time to time. I think it is a bug in the VBA
editor. Fortunately, it is harmless and you can safely ignore it.

Cordially,
Chip Pearson
Microsoft Most Valuable Professional
Excel Product Group, 1998 - 2009
Pearson Software Consulting, LLC
www.cpearson.com
(email on web site)

 

[Jarek Kujawa]

thanks a lot Chip
I am an addicted reader of your site
;-)
I am trying ignore that bug but it is a bit annoying when trying to
test/introduce changes into the code
I just have too many same VBAProjects to choose from
;-)
I thought there is a way to get rid of it somehow
thanks for your feedback