"More Controls" on the Toolbox

[John Hipskind]

There are dozens of additional controls listed under the
More Controls button of the Toolbox, some of which I
think I might like to use.
For example:
Microsoft Common Control Dialog, Ver. 6.0 (I am told I
don't have a license)
iDrop (an AutoCAD web feature; the Autodesk website has
nothing on this)
In general, how do I find out more about, and implement,
these features?
Thanks.
John

 

[Wayne Morgan]

Many of these controls will be installed with other programs. You will have the rights to
use them as a user, but not to use them as a developer. For example, if you have a program
written in VB6 and the developer of that program used some add-in controls, they may show
up in the list but you can't use them for your project. To use them for your project, you
would have to have VB6 installed on your computer. I have found that the controls will
then work in Access as well (usually). You can also buy 3rd party controls that will work
with Access. The Visual Basic forums or the Visual Basic sections in TechNet can probably
give you some good locations to look.

 

[Douglas J. Steele]

In addition to what Wayne's written, be aware that Access is somewhat
"picky" in what ActiveX objects it'll use, which means that many controls
that are available in, say, Visual Basic will not work in Access.

The following KB articles may be helpful:

ACC2000: Custom ActiveX Control Features Supported in Access 2000
http://support.microsoft.com/?kbid=202104
ACC2000: Supported ActiveX Controls for Microsoft Access 2000
http://support.microsoft.com/?kbid=208283

(don't fuss the version of Access in the KB articles: it's the same for all
versions)

 

[Marshall Barton]

There are dozens of additional controls listed under the
More Controls button of the Toolbox, some of which I
think I might like to use.
For example:
Microsoft Common Control Dialog, Ver. 6.0 (I am told I
don't have a license)
iDrop (an AutoCAD web feature; the Autodesk website has
nothing on this)
In general, how do I find out more about, and implement,
these features?

Here's some of the downside of those things, especially that
common dialog junk (the recommended alternative is
http://www.mvps.org/access/api/api0001.htm). There are
versioning (DLL Hell), distribution and installation
problems with OCX controls, many are terrible, a few are
quite good. I think it's best to avoid them if you can get
the job done any other way.

This is a good oportunity for others to jump in with their
favorite (high quality?) controls.

 

[Marshall Barton]

In reply to private email:

You have to place the api0001 code in a standard module, not
a form's class module.