![]() |
Protect VBAProject from within the code
Is there any way to Protect/Unprotect the VBAProject from within the VB code
rather than from the VisualBasic user interface? thanks, ken |
Protect VBAProject from within the code
Only using sendkeys.
-- Regards, Tom Ogilvy "Ken Soenen" wrote in message ... Is there any way to Protect/Unprotect the VBAProject from within the VB code rather than from the VisualBasic user interface? thanks, ken |
Protect VBAProject from within the code
You can keep the VB code from ever getting into the users workbook.
How's that? 1. Store the VB code in an AddIn, 2. In the template or workbook, the one having the numbers add subs like these to remove the addin reference : Private Function ReferenceExists(reference As String) As Boolean Dim result As Boolean result = False On Error Resume Next result = Not Me.VBProject.References(reference) Is Nothing ReferenceExists = result End Function Private Sub Workbook_BeforeSave(ByVal SaveAsUI As Boolean, Cancel As Boolean) If ReferenceExists("MyExcellAddin") Then WorkbookUtils.RemoveReferences Me End If End Sub |
Protect VBAProject from within the code
This might help too.
Private Sub Workbook_Open() If ReferenceExists("MyExcellAddin") Then ' We need to generate the report ReportUtils.AutoGenerateReport Me End If End Sub |
All times are GMT +1. The time now is 02:57 PM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com