zxing qr code encoder example c# Sub CallOut() Call CurrencyModule.Krona() End Sub in C#

Generator QR Code 2d barcode in C# Sub CallOut() Call CurrencyModule.Krona() End Sub

5

Creating Sub and Function Procedures When you create a new code module, the Visual Basic Editor gives it the name Module1, Module2, and so on. You should strongly consider renaming the modules in your projects to make their contents more obvious. To rename a module, follow these steps:

1 Open the workbook to which the module is attached, and click Tools, Macro, Visual Basic Editor. 2 In the Project window, click the name of the module you want to rename. 3 In the Properties window, select the existing module name next to the Name property, type the new module name, and then press Enter.

You can run into trouble if you have procedures with the same name in two or more workbooks. You can t have two procedures with the same name in a module, but because you can use dot notation to specify which module s procedure you want, you can avoid any problems. That said, if you have several procedures with the same name in dif ferent modules and you attempt to call one of them without specifying the module that con tains the procedure (for example, CurrencyModule.Krona), the Visual Basic Editor will display an Ambiguous name detected error and halt the execution of the code that attempted to call the procedure.

If you know that the procedure you want to run is available in a module attached to another workbook and for some reason don t want to copy the code to your current workbook, you can call the procedure from the other workbook in one of two ways: by using the Application.Run method and specifying the name of the workbook, or by creating a reference to the workbook that contains the procedure. Using the Application.Run method to run a procedure in another workbook requires you to name only the other workbook and the procedure you want to run. You name the workbook and procedure using a syntax that looks a lot like the reference you create when you link from a worksheet cell to a cell in another workbook.

If you wanted to call the ConvertToKrona procedure from the workbook ExchangeRates.xls, you would use the following statement:

Application.Run "'ExchangeRates.xls'!ConvertToKrona"

5

Microsoft Office Excel 2003 Programming Inside Out One limitation of the Application.Run method is that the workbook that contains the called procedure must be open to allow Excel to look into it to see what procedures are available. That requirement is the reason that the Macros dialog box can display macros in the current workbook, any open workbook, or all open workbooks: the program designers chose not to let Excel reach into workbooks unless they were already open and ready for use. You can, however, make it possible to call procedures in any workbook, open or not, by creating a reference to the procedure. Just as using the Application.Run method to call a pro cedure from another workbook is similar to creating a link from a worksheet cell to a cell in another workbook, creating a reference to a procedure in another workbook is very similar to linking or embedding an outside file in an Excel workbook. But, instead of using the Insert Object dialog box in Excel, you use the Tools, References dialog box in the Visual Basic Editor (shown in Figure 5-4).

Figure 5-4. The References dialog box lists all the available resources to which you can link and subsequently call procedures.

When you first display the References dialog box, it doesn t list the projects available in the Excel workbooks on your computer (and any network drives to which you have access), but you can go looking for them using the Add Reference dialog box. To add a reference to an Excel workbook to the list in the References dialog box, follow these steps: