I recently loaded a project group (.vbg) in VB6 which contains many
projects (15-20).  It seems that for each project loaded, the Office
2003 installer would pop up.  I would click on Cancel and then it
would pop up for the next project.  As you can imagine, this is very
annoying and I am trying to find a way stop it.

I do not have access to the Office 2003 cd because my company installs
the software on each machine.  If necessary, I could probably get it.

The other option I have is to upgrade to Office 2007 and am wondering
if that would solve the issue?

Any information that you could provide would be helpful.

Thanks,

Chris

Chris Dunaway wrote:

Show quoteHide quoteI can confirm how annoying this is. One or more of the projects has a
reference to an Office application, like Excel.Application. The only
solution I know of is to remove the reference, although the application may
no longer work until you replace the functionality.

As I recall, I also saw this where Office was once installed but later
removed, and the app uses something like Windows Explorer (if I remember
correctly). I never understood why this happened. In that case my solution
was to install Office.

Show quote Hide quote This used to be a very common problem.  You get it because there are some
shared components/files and something got screwed up (I don't think anybody
has ever definitively figured out what or how) such that Windows thinks
things needs "repaired".  Can't say that I see or hear of this problem much
anymore (or at least not nearly as much as a few years ago).  This is most
likely due to each newer version of Office using fewer files that also
installed by VB6. This problem used to be quite common with Office XP.  It's
actually not restricted to only getting prompted by the Office installer.
It's just more common with Office. It could actually happen with any
application installed using Windows Installer AND which installs certain
files that are also installed by VB's or VS's Setup.

If you click Cancel for each of these prompts, you're just going to get them
again the next time you open the project. And since you're opening a project
group with that many projects (in all honesty, gotta question how wise it is
to have *that* many projects in a project group, but that's a different
topic of discussion so I won't get into it further here), I can imagine how
annoying this would be.  But to make it a *little* less annoying, just keep
the Escape key held down, which will cancel each prompt.

Generally, when this occurs the best and easiest thing to do is pop in the
Office CD/DVD and let Windows "fix" whatever it thinks needs "fixed".
Otherwise, you're probably just going to keep on getting the prompts when
you open a project (or even just start VB).

As far as upgrading to Office 2007 solving this? Yeah, it would, but only
for the same reason that popping in the Office 2003 CD fixes the problem
too. I suppose you could use this as an excuse for upgrading to Office 2007
if that's what you want to do.  <g>  The problem might re-occur less often
with Office 2007 since it has fewer files in common (as I said, it seems to
be less of a problem with each new version of Office).

Like I said, in my company, I don't have copies of the Office 2003
CD's, so even if I wanted to put them in, I couldn't.  I requested
Office 2007 be installed and the problem has gone away

Thanks for the response,

Chris

<dunaw***@gmail.com> wrote in message
So you've traded one instability for another ;-)

Mike

<dunaw***@gmail.com> wrote in message
Show quoteHide quoteThat's not quite what you said.  <g> You said you could probably get them if
necessary.

So I guess the Office 2003 CDs are moot anyway.  Glad you got it taken care
of. Hope you like Office 2007.  Personally, I think I still prefer Office
2003. <g>

I had the same problem some years ago and - as far as I recall - fixed it by
deleting all files in the folder c:\windows\installer\ followed by running a
reg-cleaner program. If you try this suggestion it might be a good idea not
to delete the files but to move them to a "SAFEBOX" and check if the removal
has any fatal effects on the OS.

Recently, however, the problem returned (on a different pc) - and the above
procedure did not prevent the Installer msgbox from popping up every time I
open explorer.exe. This time VB is not affected, only the explorer.exe.
Despite numerous attempte to kill this msgbox - including running two
differenr reg-cleaners and running the ms clean-up utility
(http://support.microsoft.com/defaul...kb;en-us;290301) - it still keeps
popping up.

If you try Googling "windows installer keeeps popping up" you will see that
you are not the only person that encounter this misbehaviour of windows (XP
Pro).

Good luck - and please report any successes...

Soeren

Show quoteHide quote

I too have suffered from this in the past.
In my case it was the "webfolders" thingy that it was looking for
I never found out what particular reference in my project was causing this -
as soon as I added any Office object it needed webfolders.



accbc90f-c682-473b-9809-881e3a8f0***@v38g2000yqb.googlegroups.com...
Show quoteHide quote

OT: Win 3.1
optional args to a class.Init method
Save Picture Q
IE menu extension
Should Reg-free COM still utilise an installation procedure?
Gradient
Windows Update KB960715 blocks MSFLXGRD.OCX!!!!! Any solution ?
Unsigned C long to signed VB5 Long query.
Search a Combobox
Cannot pass a control array ?