Question about ActiveX

[Guest]

i have a Access 2003 database that i deploy to my customers. I have today
found some ActiveX components that i can use with my database from
http://www.namtuk.com/mycommandbutton.aspx

Ive never had anything to do with activex control before. can someone point
me in the right direction of some good articles of what they are and how they
work.

Also i have the option to purchase the activex or source code. Whats the
difference between them and which is best to purchase for an access 2003
database that gets deployed to differect customers?

Any info would be much appreciated.

 

[Douglas J. Steele]

Do not purchase ActiveX controls unless the vendor guarantees that they will
work with Access. Access is very particular about what ActiveX features it
will and won't support. If they're not sure, point them to
http://support.microsoft.com/?kbid=202104. While that article only mentions
Access 2000, it applies to all versions of Access.

In addition, be aware that anytime you add references to an Access
application, you increase the risk of the application not working when put
on another machine.

 

[Guest]

thanks for info Douglas,

what advantage would there be buying the source code rather then the
activex. what is an activex? a type of progam?

 

[Douglas J. Steele]

See whether http://www.webopedia.com/TERM/A/ActiveX_control.html helps you
understand what it is a bit better.

The advantage of having the source is that you could alter the control if
you didn't like, say, its colour and they didn't expose a property to let
you change it. However, having the source is only of use to you if you have
the software they used to create the control (likely one of the .Net
languages).

 

[Guest]

thanks for info

See whether http://www.webopedia.com/TERM/A/ActiveX_control.html helps you
understand what it is a bit better.

The advantage of having the source is that you could alter the control if
you didn't like, say, its colour and they didn't expose a property to let
you change it. However, having the source is only of use to you if you have
the software they used to create the control (likely one of the .Net
languages).

 

[aaron.kempf]

Douglas;

I've never had a problem; and I've probably used 100 different ActiveX
controls

-Aaron

 

[William Hindman]

....you need to be very careful when choosing/using third party ocx's
....Access does not implement the full ActiveX container environment and thus
many ocx's will not work/only partially work, or are not deployable except
via mde ...some are poorly written and leak resources ...in addition way too
many ocx providers do not update or support their products in a timely
manner as MS upgrades Access and thus leave you stuck in the middle with an
app that can't be upgraded without a significant rewrite.

....I much prefer to use native Access code to do many of the things that the
Activex controls normally provide ...you really should check out the full
array of native Access code solutions before deciding to use a third party
ocx ...most of them are free with full source code so you can make it do
pretty much what you want ...not always as easy the first time as an activex
control but well worth the effort ...take a look at www.lebans.com,
www.peterssoftware.com, or www.rogersaccesslibrary.com for starters ...there
are many, many more sites available with native code alternatives including
those maintained by most of the access mvps here.

....having said that, there are some good highly reputable ocx providers that
have been around a long time and have a record of working well with Access
and updating their products concurrently with MS releases ... www.fmsinc.com
and www.bennet-tec.com are two that I am personally comfortable with based
on my own experience with them ....ymmv

....hth

William Hindman