There are three different terms we use to describe tools that developers can hook into the native Microsoft Access environment: Wizards, Builders, and Add-ins. It's important to understand that there's no conceptual difference between the three. They are all constructed the same way: with Microsoft Access Basic code loaded as a library. The differences in terminology are purely for UI convention.
Wizards are typically implemented as multiple-page forms that the user navigates through using "VCR" buttons to move from page to page. Examples are the Form Wizards and Report Wizards.
Builders are typically implemented using standard Microsoft Windows® dialog box UI conventions - with OK/Cancel buttons, and so on. They usually build a single property, such as the Picture property of a Command Button.
Add-ins are tools that don't fit into either of the other two categories. They are typically invoked from the File/Add-ins submenu and can include any general-purpose utility. Examples in Microsoft Access 2.0 are the Database Documentor and the Attachment Manager.
To the developer, all three tools are implemented the same way: Microsoft Access Forms and Microsoft Access Basic Code are loaded as a library database. It's only the UI conventions that dictate the different names. We'll use the terms somewhat interchangeably in this paper.
The Add-in, in this example will help the user set the LinkMasterField and LinkChildField properties of a subform control. We have implemented it as a Builder; it appears to the user as simple dialog box and builds a property.