VB6.olb (Visual Basic Objects and Procedures)

[galenpeck]

I have an Access Project application that was originally referencing VB6.olb.
This application was packaged to distribute the vb6.olb object library. The
application appeared to install fine and work fine. But, now after the
application is uninstalled, the next time Access 2003 is started it goes
through a self-repair.
It appears that this self-repair is caused by the removal of vb6.olb during
the un-install of the application. I think this object library is included in
the VBA DLLs and probably should not have been included in the original
install.

Does anyone have any insight as to why the uninstall of this application
would cause Access to go through a self-repair? The self-repair only happens
after you try to execute VBA code.

 

[Alex Dybenko]

Hi,
are you sure you really need this reference? if no - then remove it from
list of references, if yes - then make sure that you have it installed and
registered on target OC

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

 

[galenpeck]

The VB6.OLB reference is not needed and has been removed in the current
version.

This is an application that I took over from another developer. That
developer had referenced the VB6.OLB and cretaed the install pack to install
and register that file.
The problem that I now have is from the un-install of the original version.
When the VB6.OLB gets un-installed it seems to mess up Access's VBA
references and forces Access to do a self-repair.

 

[Alex Dybenko]

hi,
VB6.OLB is a part of visual basic 6, don't know if it cause Access
self-repair. Perhaps something else cause this? maybe he included there
other libraries, which really used by access and get uninstalled by his
install pack?

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com