By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,080 Members | 1,855 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,080 IT Pros & Developers. It's quick & easy.

Remove form from Project Explorer window

P: 15
This seems to be rather a silly question but how do I remove a form from the VBA Project Explorer window? When I first setup the database, the form in question contained VBA code so it was included in the Project Explorer window. As the database has evolved (well, mostly as I have evolved), the coding changed such that the form is still in use but no longer has any code.

Since there are a number of forms, subforms, and reports, I would prefer to only see the ones with VBA code in my Project Explorer. I have been playing with this for quite a while and have not reached any solution beyond recreating the form from scratch but without the code this time. Any ideas?
Jul 30 '08 #1
Share this Question
Share on Google+
8 Replies

Expert 100+
P: 1,923
You can close the project explorer window by setting focus to the applicable window, and clicking the X in the upper right corner. To re-open hit CTRL-R Keys.
Aug 1 '08 #2

Expert Mod 15k+
P: 31,494
In the properties of your form (Design View) set "Has Module" to No.

This should produce the effect you're after.

PS. It will also lose ALL code you may still have in that object (the form) so don't expect to be able to return from this change later.
Aug 5 '08 #3

P: 15
Exactly what I was looking for, NeoPa. Thanks so much!
Aug 5 '08 #4

Expert Mod 15k+
P: 31,494
No worries Rach - Pleased to help :)

Welcome to BYTES!
Aug 5 '08 #5

Expert 2.5K+
P: 3,532
As the database has evolved (well, mostly as I have evolved), the coding changed such that the form is still in use but no longer has any code.
I'm fascinated with the idea of evolving to the point where my forms don't require any code!

Welcome to Bytes, RachH!

Linq ;0)>
Aug 5 '08 #6

Expert Mod 15k+
P: 31,494
Possibly there are references now to controls on the form, whereas before the controls had their info passed using code in the AfterUpdate events or something similar.
Aug 5 '08 #7

P: 15
It was something like that. The forms in question were subforms and, using the master/child interaction, I figured out a more efficient way to accomplish what the code had originally accomplished. It was very much a matter of my understanding of Access having evolved. And believe me, the amount of code I added to other forms more than makes up for the few forms that were stripped of their code!
Aug 7 '08 #8

Expert Mod 15k+
P: 31,494

Looking back over the stuff in my databases, I can see where I wrote stuff before I understood certain things.

I try to bring older stuff up-to-date when I can, but there's so much there now that's getting quite impractical - even for just my main database.
Aug 7 '08 #9

Post your reply

Sign in to post your reply or Sign up for a free account.