G
Gregg
Steve said:Note that this may toss errors if access to VB project isn't trusted in
Security settings (or if the file hasn't been saved once)
Of course, with or without Debug.Print, programmatically removing a
module from the VBE causes an error if permission isn't ticked in the
Security settings. Assuming the target file is active, my core code
alone can trigger the error.
Sub RemoveModule()
Dim vbcompX As VBComponent
Set vbcompX = ActivePresentation.VBProject. _
VBComponents("TempMacros")
ActivePresentation.VBProject.VBComponents.Remove vbcompX
End Sub
Luckily, I can handle that part.