XL: Securing Visual Basic Code in Microsoft ExcelID: Q167909
|
In Microsoft Excel 97, unlike earlier versions of Microsoft Excel, you
cannot hide Visual Basic for Applications modules. If you want to prevent
users from seeing Visual Basic code, you can lock the Visual Basic project
in the workbook and prevent users from viewing it. However, if you save
the workbook in either the Microsoft Excel 5.0/95 or the Microsoft Excel
97 & 5.0/95 file format, the module protection is lost when you open the
workbook in Microsoft Excel 5.0 or 7.0. Therefore, to use this method, you
must maintain separate versions of the workbook for users of Microsoft
Excel 97 and users of Microsoft Excel 5.0 and 7.0.
This article describes a method of protecting Visual Basic code while
allowing users of different versions of Microsoft Excel to use the same
version of your application. This method requires that you create the
application in Microsoft Excel 5.0 or 7.0 and then save it as an add-in
file. This method hides the code in all versions of Microsoft Excel. Any
add-in code you create in Microsoft Excel 5.0 or 7.0 is not visible when
the file is opened in Microsoft Excel 97.
In the example in this article, you compile an application into an add-in
file. The interface for the application consists of two worksheets, which
are copied into a new workbook when the add-in file is opened.
NOTE: To create an add-in that is compatible with Microsoft Excel 5.0 and
7.0 and Microsoft Excel 97, use the earliest version of Microsoft Excel
in which the add-in will be used. For example, if you use Microsoft Excel
7.0 and Microsoft Excel 97, create the add-in in Microsoft Excel 7.0.
Microsoft provides programming examples for illustration only, without
warranty either expressed or implied, including, but not limited to, the
implied warranties of merchantability and/or fitness for a particular
purpose. This article assumes that you are familiar with the programming
language being demonstrated and the tools used to create and debug
procedures. Microsoft support professionals can help explain the functionality
of a particular procedure, but they will not modify these examples to
provide added functionality or construct procedures to meet your specific
needs. If you have limited programming experience, you may want to contact
the Microsoft fee-based consulting line at (800) 936-5200. For more
information about the support options available from Microsoft, please see
the following page on the World Wide Web:
http://www.microsoft.com/support/supportnet/refguide/
' This subroutine copies the worksheets to use as the interface
' for the application into a new workbook each time that the
' add-in is opened.
Sub Auto_Open()
Dim NewBook As Workbook
Dim Ctr As Integer
Application.ScreenUpdating = False
Application.DisplayAlerts = False
' Create a new workbook.
Set NewBook = Workbooks.Add
' Copy the two worksheets into the new workbook.
ThisWorkbook.Sheets(Array("AddinSheet1", "AddinSheet2")).Copy _
before:=NewBook.Sheets(1)
' Delete all of the other sheets in the new workbook. The
' initial value of the counter is 1 greater than the number of
' worksheets that you want to copy into the new workbook.
For Ctr = 3 To NewBook.Sheets.Count
NewBook.Sheets(3).Delete
Next
End Sub
' This sample demonstrates that any buttons that you place on the
' interface worksheets are still functional when the worksheets are
' copied into a new workbook.
Sub Test()
MsgBox "This is a test"
End Sub
"Visual Basic User's Guide," version 5.0, Chapter 13, "Converting a
Workbook to an Add-in Application"
For more information about creating add-ins in Microsoft Excel 7.0, click
the Index tab in Microsoft Excel Help, type the following text
add-ins, creating in Visual Basic
Additional query words: XL97 secure securing protect
Keywords : kbmacro kbprg kbui xlvbahowto xlvbainfo xladdins
Version : WINDOWS:5.0,7.0,97
Platform : WINDOWS
Issue type : kbhowto
Last Reviewed: May 17, 1999