Re: MSI Installer now pops up when running VB app

We upgraded the office server so had to create a new User account on my
PC to connect to the new server. "They" were supposed to copy all User
profile settings to the new User...but...they apparently missed some DLL
or OCX registration(?).

Now, when I start any of my VB apps Microsoft Installer (MSI) pops up
wanting to reinstall some old software. Apparently the original software
that registered the offending DLL or OCX is not longer installed properly
and MSI wants to 'repair' it. I did have the CD for the 1st software it
was complaining about and that helped, but, when I got further into the
app MSI pops up again. This time I do not have the CD to reinstall that
old software. Unfortunately MSI does not say what component it is
looking for. Event Viewer does not either.

Where are DLL and OCX registrations saved and how can I remove/change
them?
thx


Hello Joe,
I usually have this problem when installing an MS-Office upgrade, and then
run an application that uses an older version of DAO.
Install the most current MDAC on the machine and see if that helps.
Regards,
David

Neither the app I'm trying to run or the old app that originally registered
the OCX or DLL (or some other element) use any dataBase component. Doing
some Googling shows that this error occurs when an old app is broken (i.e.
registry error) and Windows/MSI tries to repair it. The old app is broken
because not all User profile setting were copied over correctly or
completely.

Someone has to know how/where OCXs and DLLs are registered and the app that
is associated with such.(?)

TIA



.

Relevant Pages

  • Re: DLL or OCX?
    ... OCX - geared towards GUI components, like grids, textboxes, combos, ... DLL - geared towards non-displayable components. ... capture a special number that has to be captured in three textboxes. ... number will be captured at various points in your app. ...
    (microsoft.public.vb.general.discussion)
  • Re: Registering DLL Question - Part 2
    ... DllMain is the first thing that is called in any DLL. ... they leave the registry entries alone. ... the program added the OCX to the registry by some unknown force. ... By updating app B and releasing it with the new third ...
    (microsoft.public.vb.enterprise)
  • Re: MDI Child form in DLL
    ... Your app or DLL or OCX could query a permissions table to see ... You can either use this (from the app) to turn on and off menu ...
    (microsoft.public.vb.general.discussion)
  • Re: Debugging dll newb question
    ... > with a vb6 dll project open in an instance of vb6ide ... > then in a vba ide running in another app, i reference and use the dll to ... Hijacks the Registry. ... > why am i not haveing to register the ocx either? ...
    (microsoft.public.vb.general.discussion)
  • Re: Delphi DLL / VB app
    ... > But the real VB app ... But I quess your Delphi written ActiveX component appeared to the VB ... then VB should be aware about your DLL and ActiveX ... I use Delphi's TREGSVR.EXE for those registrations. ...
    (comp.lang.pascal.delphi.misc)