Microsoft KB Archive/208196

= ACC2000: Using Lightweight Objects in Access =

Article ID: 208196

Article Last Modified on 12/12/2002

-

APPLIES TO


 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q208196



This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).

Moderate: Requires basic macro, coding, and interoperability skills.

For a Microsoft Access 2002 version of this article, see 324589.



SUMMARY
This article describes the concept of lightweight objects and provides a technique to create a lightweight switchboard form that uses the Hyperlink properties of form controls to open other objects in the database.

NOTE: This article explains a technique demonstrated in the sample file, FrmSmp00.mdb. For information about how to obtain this sample file, please see the following article in the Microsoft Knowledge Base:

233324 Microsoft Access 2000 Sample Forms Database Available in Download Center



MORE INFORMATION
Lightweight forms and reports, which are objects that do not contain a class module, were first introduced in Microsoft Access 97. One advantage of lightweight objects is that they are smaller and typically load and are displayed faster than objects with class modules. Also, because they require no storage space for a class module, they can decrease the size of your database. Possible disadvantages of using lightweight objects is that they do not appear in the Object Browser, and you cannot use the New keyword to create a new instance of the object.

When you create a new form or report, it is a lightweight object by default. Access creates a class module for the object only if you do any of the following:
 * Add Visual Basic code to an event property in the object.
 * Open the object in Design view, and then click Code on the View menu.
 * Set the HasModule property of the object to Yes.

You can convert an object with a class module into a lightweight object by setting its HasModule property to No, and then saving the object.

WARNING: If an object has a class module, and you save the object with a HasModule property set to No, its class module and any code it contains are deleted.

Making an object Lightweight
If you need an object to perform certain actions assigned to events, there are techniques to doing this without adding any modules to the form.

Method 1
If the code is not very complex, you can re-write it as a macro and have the event call the macro instead of the code. If you call a macro, the form remains lightweight.

For example, if on a form you have a Click event for a command button that previews a report called Sales by Category, you could create the following macro called RunReport   RunReport Action Arguments ---  OpenReport Report Name: Sales by Category View: Print Preview and then set the OnClick property of the command button to the following:

RunReport

NOTE: If you want your macro to perform some actions and then to run Visual Basic for Applications code to do the rest, you can have the macro call a Visual Basic for Applications function with the command RunCode, as in the following example:   RunReport Action Arguments ---  OpenReport Report Name: Sales by Category View: Print Preview

RunCode Function Name: MyFunction

Method 2
You can also have the event assigned to the object call a public function. An object is still lightweight if it has an event that calls a public function. Using the example in Method one, you could write a generic function that runs reports and place that in a public module. You can then call that function from the Click event. To see how this works, follow these steps:

CAUTION: If you follow the steps in this example, you modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and follow these steps on a copy of the database.

 Open the Northwind sample database. In the Database window, click Modules under Objects, and then click New.  In the new module, type or paste the following function: Function ShowReport(txtReport As String) DoCmd.OpenReport txtReport, acViewPreview End Function  Save the module and close the Visual Basic Editor. In the Database window, click Forms under Objects, and then click New</li>  Create the following form: <pre class="fixed_text">  Form: frmMyform -  Caption: fromMyform ControlSource:

Command button -  Name: Button0 Caption: My Button OnClick: =ShowReport("Sales by Category") </li> View the form in Form view, and click the command button.</li></ol>

Note that you receive the preview of the Sales by Category report.

By using this method, the form has no module behind it, and therefore it is a lightweight form. Yet, you have the ability to call Visual Basic for Applications code. And you can still specify which report you want to preview in the Click event.

Method 3
By using the Hyperlink property of command button controls, label controls, and image controls, you can create a lightweight switchboard form in your database that does not use any Visual Basic code or macros.

The following example creates a switchboard form that demonstrates the use of hyperlinks to open database objects: <ol> Open the sample database Northwind.mdb.</li>  Create the following new form not based on any table or query in Design view: <pre class="fixed_text">  Form: MySwitchboard --  Caption: Main Menu

Command button ---  Name: OpenEmp Caption: Employees Form HyperlinkSubAddress: Form Employees

Label ---  Name: OpenCat Caption: Catalog Report HyperlinkSubAddress: Report Catalog

Image ---  Name: OpenSales Picture: C:\Windows\Circles.bmp PictureType: Embedded SizeMode: Clip PictureAlignment: Center PictureTiling: No  HyperlinkSubAddress: Query Category Sales for 1995 NOTE: If you do not have the file C:\Windows\Circles.bmp, you can substitute another bitmap or graphic file on your computer in the Picture property of the image control.

Note that the HasModule property of the form is set to No. That is how you can tell that this is a lightweight form. </li> Save the MySwitchboard form, and then open it in Form view.</li> Click the Employees Form button, the Catalog Report label, and the image control and note that each one opens the object specified in its HyperlinkSubAddress property.</li></ol>

<div class="references_section">