Re: DLL or OCX?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Saga (antiSpam_at_somewhere.com)
Date: 08/26/04 

Date: Thu, 26 Aug 2004 15:01:15 -0500

A "normal"application is a standard EXE. The application uses OCXes
and DLLs, which are components. These are used by other apps, and are
not applications by themselves.

OCX - geared towards GUI components, like grids, textboxes, combos,
lists, and so on. So if you need a custom made user interface component,
make an OCX.

DLL - geared towards non-displayable components. If you need to do
some processing, having nothing to do with GUI components, then you
can place your code in a DLL.

Again... first you select the kind of app you want, like the Standard
EXE
mentioned above, on the form you place user interface (UI) components.
If
you need a UI component that is not available, then you make an OCX
that implements the component you want. A simple example. You need to
capture a special number that has to be captured in three textboxes.
This
number will be captured at various points in your app. So instead of
placing
three textboxes evryplace you need to capture this number, you build an
OCX
that contains these three textboxes, along with any validationor
preprocessing
code that is necessary. Once the OCX is built, you can insert it as many
times
as you need. The OCX by itself can't do much, but it can become an
important
support device in your app. Same with the DLL, except that the DLL only
contains code and will not be used as a UI component.

If your app needs to do some processing then you build code to do the
job.
If you see that this code will be used often in other projects, then you
can
make DLL and place the code there. Now all you have to do is reference
the DLL and it is ready to be used.

I hope this helps

Best of luck in your endeavors
Saga

"Marty" <reply@to.forum> wrote in message
news:3oqXc.46291$jZ5.41656@clgrps13...
> Hi,
>
> If my goal is to make my app as fast as possible should I use an OCX
or
> a DLL ?
>
> I'll make it as an OCX or a DLL and I don't know wich is faster. Is
> there one that, at run time, is independant from the application main
> thread? So it won't get delayed by the rest of the application?
>
> Thanks
>
> Marty

Relevant Pages

  • Re: MSI Installer now pops up when running VB app
    ... or OCX registration. ... that registered the offending DLL or OCX is not longer installed properly ... Where are DLL and OCX registrations saved and how can I remove/change ... Neither the app I'm trying to run or the old app that originally registered ...
    (microsoft.public.vb.controls)
  • Re: Firefox and Sound
    ... number of loads that app performed. ... only references to entry points in the dll. ... specified entry points in it can't be found, ... but the download manager said it was only 78.8 MB. ...
    (comp.os.os2.apps)
  • Re: New Delphi roadmap is coming: NO UNICODE PLEASE!
    ... Avoids DLL hell, because it ... The app is deployed and the user is getting an error. ... instances where upgrading .NET broke things that were working. ... Coming from Delphi, this isn't any big deal of course. ...
    (borland.public.delphi.non-technical)
  • Re: What programming language for Future
    ... usually when apps come with scripts, those scripts are for that version ... version of the app. ... Which is exactly the same as when the compiler is shipped with the app. ... for the sole reason that they can't rebuild a working dll. ...
    (comp.lang.misc)
  • Re: RPC_E_CANTCALLOUT_ININPUTSYNCCALL
    ... when trying to use an IDispatch pointer from another process. ... handler that is triggered by one of the SendMessage...functions. ... As the user interacts with the target process, the DLL will periodically ... notify the my app that it needs to take a look at the data. ...
    (microsoft.public.win32.programmer.ole)