Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
programatically deleted code still triggers macro warning
I am using code posted by Chip Pearson to programatically delete a
button and its associated code. The file from which the button and code are deleted is then saved and automatically inserted into an e- mail. When the attached file is opened directly from the e-mail (which the receiving customer will necessarily do) the macro warning still appears. The button code appears to be gone and when I try to clean the project with Rob Bovey's slick code cleaner, the file from which I have deleted the code does not show up as an option, which I believe indicates that there is no code. Also, if I save the file and reoopen it, I do not get the macro warning on the second opening. The code I am using is to delete the code is: Set WS = Workbooks(nWB).Worksheets("Quote") With WS .OLEObjects(CommandButtonName).Delete Set CodeMod = Workbooks(nWB).VBProject.VBComponents(.CodeName).C odeModule End With With CodeMod .DeleteLines StartLine:=1, Count:=.CountOfLines End With When the whole routing is completed the button is gone and the code no longer appears; but, I get the macro warning. Is there something else I need to add to make it understand that once this is accomplished there is no more code and therefore no need to prompt the user with the macro warning? Thanks Ken |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
ActiveX warning after control is deleted | Excel Programming | |||
Code & modules are gone, Macro warning message remains | Excel Programming | |||
Deleting macro code programatically | Excel Programming | |||
getting a macro warning, even through there is no code | Excel Programming | |||
code for lookup,& triggers. | Excel Programming |