AnsweredAssumed Answered

VBA editor fundamental questions swp files and projects

Question asked by Gordon Rigg on Jan 20, 2021
Latest reply on Jan 26, 2021 by Deepak Gupta

Like • Show 0 Likes0
Comment • 5

I don't understand the tree of projects and stuff works in the top left of the VBA editor window.

It appears that I am accidentally linking my macros in some way... and I don't understand how or why it does this, and what you are supposed to do - because I'm obviously not doing it right!

I edit a macro and I have one set of stuff under a bold heading here.
I open a second macro for editing. I don't get a new instance of a separate VBA editor, I get a second tree of stuff I don't understand the workings of, in this window. I can swap between the two macros and edit them.

What I cant seem to do is save and close just one of them, or save just one of them to a new *. swp name

I am obviously missing some basic fundamental understanding here...

I may have inadvertently linked more than one macro SWP file here, perhaps into a single project? how do projects relate to separate swp files? nothing I can find explains that...

To my dismay/horror I find opening some of my swp files for editing from a new session, and I have several trees of stuff in this window, and I can open different windows of completely different code that is nothing to do with what I'm doing and I though was contained in totally unrelated swp files... I opened one swp file. why is code from the swp file I opened last month showing? I fear I have destroyed one of my working macro swp files accidentally when it might have been editable without me intentionally opening it.

I can find no explanation of how this tree structure works, and how it relates to separate swp files, how to purge it of the stuff I don't want there? if I have opened several macros swp files in this window, how to save and close one without affecting the others.

Has anyone got a link to a simple (from zero knowledge of vba) explanation of how this window (and the other windows) work? and how they relate to separate swp macro files?

Deepak Gupta Jan 20, 2021 12:31 PM

Correct Answer

You can correlate the macro editor to SOLIDWORKS. Like in SW, you can open several files and they appear in same session and not in different SW sessions/instances. Similar is the case when you open macros.

You can activate the macro you want to make changes to and then click on save button to save the changes. And to close any particular macro (in case you have several open), simple click this close button or right side.

See the reply in context

No one else had this question

Outcomes

Deepak Gupta Jan 20, 2021 12:31 PM

Actions

Gordon Rigg @ Deepak Gupta on Jan 22, 2021 3:31 AM

thank you Deepak Gupta

Actions

Gordon Rigg @ Deepak Gupta on Jan 26, 2021 7:53 AM

Your answer doesn't seem to be as correct as I had first thought and I am still struggling to understand what is open, and which files can be affected and which are securely saved so they cannot be affected - edited, accessed and copied from, but not saved.
I see that clicking the x as you suggest "closes" (but actually only hides) the macro that was being edited. however it still seems that it is "loaded" in the VBA editor. it is not actually closed by hitting that X, which I'm expecting to discard all changes. It seems to be still loaded but hidden and is still saved (unintentionally, and perhaps disastrously) when I hit the save icon.
Here I have two projects "loaded" but it is impossible for me to find so far how to close one out, make it vanish from the tree. Every macro I opened for editing in the session is displayed there and it seems to be "loaded" but hidden.
I try to understand if one of the other projects could be edited, not saved but hidden, and then when i hit the save icon it saves all of them? including the ones that are not visibly open for editing? or just the one that is displayed? in this screen shot none? because I most certainly have saved files that were most definitely not obviously still open for editing - saving changes I thought I had discarded.

Explanations of how this window works seem to be very hard to find. So I have to ask it here
I am still missing some simple understanding of how its supposed to work, and need to understand this because having to exit the session each tome just to securely save macros that were loaded in the background is crazy and onerous.
A way to definitely close out a macros files and get rid of them from that tree without closing the whole session must be possible surely?

Your suggested click on the x doesn't actually do that.

I am certainly doing something very wrong here.

Actions

Gordon Rigg @ Gordon Rigg on Jan 26, 2021 8:33 AM

I got a bit further.
Only the active macro is saved with the save icon.
The inactive ones are open, hidden and not save.
existing to return to solidworks produces a save prompt for the macros that were open in the background, if they had unsaved edits.
So far no way to close out inactive unwanted macros in the tree and make them go away though, without closing the session. That facility would be nice.

Actions

Deepak Gupta @ Gordon Rigg on Jan 26, 2021 9:42 AM

Gordon Rigg wrote:

So far no way to close out inactive unwanted macros in the tree and make them go away though, without closing the session. That facility would be nice.

You can activate the hidden or unwanted macro by clicking on their module (on left side) and then click on the X button/icon on right side.

Actions

5 Replies

Deepak Gupta Jan 20, 2021 12:31 PM
Unmark Correct
Correct Answer
You can correlate the macro editor to SOLIDWORKS. Like in SW, you can open several files and they appear in same session and not in different SW sessions/instances. Similar is the case when you open macros.

You can activate the macro you want to make changes to and then click on save button to save the changes. And to close any particular macro (in case you have several open), simple click this close button or right side.
Like • Show 2 Likes2
Actions
- Gordon Rigg @ Deepak Gupta on Jan 22, 2021 3:31 AM
  Mark Correct
  Correct Answer
  thank you Deepak Gupta
  Like • Show 0 Likes0
  Actions
- Gordon Rigg @ Deepak Gupta on Jan 26, 2021 7:53 AM
  Mark Correct
  Correct Answer
  Your answer doesn't seem to be as correct as I had first thought and I am still struggling to understand what is open, and which files can be affected and which are securely saved so they cannot be affected - edited, accessed and copied from, but not saved.
  I see that clicking the x as you suggest "closes" (but actually only hides) the macro that was being edited. however it still seems that it is "loaded" in the VBA editor. it is not actually closed by hitting that X, which I'm expecting to discard all changes. It seems to be still loaded but hidden and is still saved (unintentionally, and perhaps disastrously) when I hit the save icon.
  Here I have two projects "loaded" but it is impossible for me to find so far how to close one out, make it vanish from the tree. Every macro I opened for editing in the session is displayed there and it seems to be "loaded" but hidden.
  I try to understand if one of the other projects could be edited, not saved but hidden, and then when i hit the save icon it saves all of them? including the ones that are not visibly open for editing? or just the one that is displayed? in this screen shot none? because I most certainly have saved files that were most definitely not obviously still open for editing - saving changes I thought I had discarded.
  Explanations of how this window works seem to be very hard to find. So I have to ask it here
  I am still missing some simple understanding of how its supposed to work, and need to understand this because having to exit the session each tome just to securely save macros that were loaded in the background is crazy and onerous.
  A way to definitely close out a macros files and get rid of them from that tree without closing the whole session must be possible surely?
  Your suggested click on the x doesn't actually do that.
  I am certainly doing something very wrong here.
  Like • Show 0 Likes0
  Actions
  - Gordon Rigg @ Gordon Rigg on Jan 26, 2021 8:33 AM
    Mark Correct
    Correct Answer
    I got a bit further.
    Only the active macro is saved with the save icon.
    The inactive ones are open, hidden and not save.
    existing to return to solidworks produces a save prompt for the macros that were open in the background, if they had unsaved edits.
    So far no way to close out inactive unwanted macros in the tree and make them go away though, without closing the session. That facility would be nice.
    Like • Show 0 Likes0
    Actions
    - Deepak Gupta @ Gordon Rigg on Jan 26, 2021 9:42 AM
      Mark Correct
      Correct Answer
      Gordon Rigg wrote:
      
      So far no way to close out inactive unwanted macros in the tree and make them go away though, without closing the session. That facility would be nice.
      You can activate the hidden or unwanted macro by clicking on their module (on left side) and then click on the X button/icon on right side.
      Like • Show 0 Likes0
      Actions

VBA editor fundamental questions swp files and projects

Outcomes

Related Content

Recommended Content