You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the Save command in the VBE will save all changes to the active VBProject, and to the underlying host document/file.
Access presents something similar, if one of the dirty objects is a document-type module:
It might be useful to add an option in Rubberduck, that asks the user which specific components they'd like to save, rather than persisting all changes without confirmation.
The text was updated successfully, but these errors were encountered:
ThunderFrame
added
the
enhancement
Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope.
label
Dec 9, 2017
By default, the Save command in the VBE will save all changes to the active VBProject, and to the underlying host document/file.
Access presents something similar, if one of the dirty objects is a document-type module:
It might be useful to add an option in Rubberduck, that asks the user which specific components they'd like to save, rather than persisting all changes without confirmation.
The text was updated successfully, but these errors were encountered: