>it all started when MS had this language called Visual Basic
>and one nifty feature they added was the ability to extand its
>functionality by adding
>libraries called VBXs
>the next evolutionary state was called OCXs (if I am not skipping a stage)
>these were OLE2 complient
>and come in 2 flavoures 16-bit and 32-bit (32-bit OCXs are the minimum that
>may work with VFP)
>the next step is called ActiveX controls these are 32-bit OCXs with the
>added ability to be run over Inter/intranet and stricter rules for writing
>them
>
>all of the above mentioned are basically objects that encapsulate a
>behavior and reveals some properties and methods to let you work with them
>
>HTH
>
>Arnon
>
>
>:
>: Hi all,
>: I know this is surely dummy, but can you please explain to me what are
>: OCX controls ( objects? ), how it works, and how is it connected with
>: ActiveX controls? I'm just confused from such things and I would like
>: have it clear.
>: TIA
>: Dezider
>:
>: --
>:

Don't forget ActiveX works at the binary level and is compatible with multiple platfoms.

Tom