Re: A very simple OCX Question for experts

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"Ken Halter" <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:e8M0kPdnFHA.3120@xxxxxxxxxxxxxxxxxxxxxxx

>
> imo, it's best to keep your OCX's out of Sys32.... and keep them in a
> folder that's either the same as the app that requires them or a sub
> folder off of the apps main folder. Sys32's cluttered enough <g> Uninstall
> utilities that don't work correctly, leave ocx's/dll's behind and they end
> up cluttering up Sys32 for years.

Ken, I agree with you as long as the OCX/DLL is not shared among multiple
vendors. For example, the OCXs included with VB should never (IMO) be
installed to the application folder (or anywhere other than System32)
because too many different applications from different vendors use them.
Let's say a user installs your app which installs the latest version of
MSCOMCTL.OCX in the application folder. Then, the user installs another app
from another vendor that installs a much older version of MSCOMCTL.OCX in
System32. Your app's now going to use that older version, which may
adversely affect your program.

In the case of OCXs/DLLs written specifically for a particular app, yes, I
agree it should get installed in the app's folder. I'd even go so far as to
say that OCXs/DLLs written by a vendor for use with only that vendor's
programs, install them to a "shared" folder other than System32, along the
lines of "\Program Files\Common Files\Microsoft Shared".

--
Mike
Microsoft MVP Visual Basic


.

Relevant Pages

  • Re: A very simple OCX Question for experts
    ... > because too many different applications from different vendors use them. ... > Let's say a user installs your app which installs the latest version of ... > MSCOMCTL.OCX in the application folder. ... > app from another vendor that installs a much older version of MSCOMCTL.OCX ...
    (microsoft.public.vb.general.discussion)
  • Re: Newbie Questions
    ... applications folder within their home folder for apps they do not wish ... > the switched-to app's body window to the foreground and sometimes not. ... > also not do it when none of my apps is the current app. ... > - How can I play a song with iTunes without bringing up an iTunes UI? ...
    (comp.sys.mac.system)
  • Re: Security Exception when deploying a VB.NET 2003 Solution
    ... It runs fine on any workstation. ... folder 2 levels up from the BIN folder where the application resides. ... Microsoft .NET security errors upon trying to start the Executable. ... I bet the workstaion is WinXP and your app is trying to write data( ...
    (microsoft.public.vsnet.general)
  • Re: Design Guidelines for Non-Power Users?
    ... Non-Power Users and Admins will not be able to install your app. ... You can get whatever this folder happens to be by ... If they don't have write permissions, ...
    (microsoft.public.vb.winapi)
  • Re: Cant save DB on close
    ... thus it can't close it in the normal manner and it then just shuts down. ... it is no longer listed in that folder. ... When I open the backup file it opens fine and it may go along fine for a few ... The original app was created in 2003, and I have not converted it to the 2007 format yet, as I often access it from another machine that does not yet have the 2007 installed. ...
    (microsoft.public.access.forms)