Remove form from Project Explorer window

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • RachH
    New Member
    • Mar 2008
    • 15

    Remove form from Project Explorer window

    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?
  • puppydogbuddy
    Recognized Expert Top Contributor
    • May 2007
    • 1923

    #2
    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.

    Comment

    • NeoPa
      Recognized Expert Moderator MVP
      • Oct 2006
      • 32662

      #3
      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.

      Comment

      • RachH
        New Member
        • Mar 2008
        • 15

        #4
        Exactly what I was looking for, NeoPa. Thanks so much!

        Comment

        • NeoPa
          Recognized Expert Moderator MVP
          • Oct 2006
          • 32662

          #5
          No worries Rach - Pleased to help :)

          Welcome to BYTES!

          Comment

          • missinglinq
            Recognized Expert Specialist
            • Nov 2006
            • 3533

            #6
            Originally posted by RachH
            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)>

            Comment

            • NeoPa
              Recognized Expert Moderator MVP
              • Oct 2006
              • 32662

              #7
              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.

              Comment

              • RachH
                New Member
                • Mar 2008
                • 15

                #8
                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!

                Comment

                • NeoPa
                  Recognized Expert Moderator MVP
                  • Oct 2006
                  • 32662

                  #9
                  LOL

                  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.

                  Comment

                  Working...