Total Access Components is the only collection of ActiveX controls specifically designed and tested for Microsoft Access. There are 27 ActiveX controls included in Total Access Components. You can place them on your forms and reports to enhance your application�s ease of use, appearance, and operation. Many controls allow you to provide new and enhanced display effects, while others allow you to use properties and methods to perform complex operations with little or no programming.

Microsoft Access has supported ActiveX controls. Unfortunately, ActiveX controls designed for Visual Basic do not necessarily work in Access. Total Access Components is designed exclusively for Access, fully tested on Access, and optimized for Access and the needs of Access developers. If you are considering using ActiveX controls in Access, make sure the vendor understands Access and verifies their controls work in it. Very few do.

Easy to Use
Simply place a Total Access Components control on your form or report just like a built-in Access control (e.g. text box, combo box, etc.). You can set its properties interactively or programmatically. Many controls can be bound directly to a field.

There are visible controls like tabs, gauges, progress meters, etc. and invisible controls such as clipboard functions, common dialogs, form resizer, etc. Invisible controls are also placed on forms and reports but are not visible to the user. Set its' properties and invoke a one line method to run it. That's all it takes to add Windows dialogs, form resizers, etc.!

All Controls in One File
All 27 controls in Total Access Components are stored in one OCX file. Most commercial ActiveX controls for Visual Basic store each control in a separate OCX file. The one file design for Total Access Components is superior and very important for Access developers:

Performance: If you use more than one control, the loading time for the second control is much faster when they are stored in one file.

Size: The entire OCX file of 27 controls is under 550K. That may be a lot for a VB program, but it is not much for an Access application. By using just one file, a lot of overhead is eliminated and it is much smaller than 27 individual files.

Distribution: Access doesn't tell you which ActiveX controls are used in a database. Trying to remember which of the 27 controls you used would be a pain and subject to error. Thankfully, you do not need to remember that. With Total Access Components if you remember using any of its controls, add its OCX file in your distribution (setup) program and that's it. No need to wonder whether you missed one or not.