Hi All

Have installed VB6 and MSDN on to my new laptop, It's Winders 7 64bit. I got 
2 problems (amongst others):
1. Each time VB6 starts I get a box saying Please wait while winders 
configures micro$oft office 2007. It then tells me it cannot find required 
files, It does this 4 times. This PC used to have a trial version of office 
installed but no longer has. How to stop it doing this?
2. A full install of MSDN was done a few times, MSDN is missing those links 
at the top of the help file pages. Things like 'See Also, Properties, 
Methods, Events, Applies to'. Where have my links gone?

Any help appreciated

Ivar 

"Ivar" <ivar.ekstrome000r@ntlworld.com> wrote in message 
news:#5ZYvfXsKHA.732@TK2MSFTNGP06.phx.gbl...
> Hi All
>
> Have installed VB6 and MSDN on to my new laptop, It's Winders 7 64bit. I 
> got 2 problems (amongst others):
> 1. Each time VB6 starts I get a box saying Please wait while winders 
> configures micro$oft office 2007. It then tells me it cannot find required 
> files, It does this 4 times. This PC used to have a trial version of 
> office installed but no longer has. How to stop it doing this?
> 2. A full install of MSDN was done a few times, MSDN is missing those 
> links at the top of the help file pages. Things like 'See Also, 
> Properties, Methods, Events, Applies to'. Where have my links gone?
>


First, *please* quit calling Windows "Winders". That's just juvenile. You're 
not even saving any keystrokes since both are 7 characters.  <g>

2nd, both these questions have been asked repeatedly and answered.  Try 
searching the newsgroup archives at www.google.com BEFORE posting.  Chances 
are, the question has already been asked. The benefit to you is that you 
don't have to wait for someone to post an answer.

Thanks for helping make the newsgroups better.  <g>

-- 
Mike
 

"MikeD" <nobody@nowhere.edu> wrote in message 
news:%23btNKCZsKHA.4752@TK2MSFTNGP04.phx.gbl...

>> "Ivar" <ivar.ekstrome000r@ntlworld.com> wrote in message 
>> news:#5ZYvfXsKHA.732@TK2MSFTNGP06.phx.gbl...
>> Have installed VB6 and MSDN on to my new laptop,
>> It's Winders 7 64bit.
>
> First, *please* quit calling Windows "Winders". That's just juvenile.

Is it okay if I continue to call it Windoze?

Mike

Mike Williams wrote:
> "MikeD" <nobody@nowhere.edu> wrote in message 
> news:%23btNKCZsKHA.4752@TK2MSFTNGP04.phx.gbl...
>
>>> "Ivar" <ivar.ekstrome000r@ntlworld.com> wrote in message 
>>> news:#5ZYvfXsKHA.732@TK2MSFTNGP06.phx.gbl...
>>> Have installed VB6 and MSDN on to my new laptop,
>>> It's Winders 7 64bit.
>>
>> First, *please* quit calling Windows "Winders". That's just juvenile.
>
> Is it okay if I continue to call it Windoze?

Another recently cited variation... Weven. <eye roll>

-- 
..NET: It's About Trust!
http://vfred.mvps.org

On Fri, 19 Feb 2010 15:26:45 -0000, "Ivar" <ivar.ekstrome000r@ntlworld.com> wrote:

� Hi All
� 
� Have installed VB6 and MSDN on to my new laptop, It's Winders 7 64bit. I got 
� 2 problems (amongst others):
� 1. Each time VB6 starts I get a box saying Please wait while winders 
� configures micro$oft office 2007. It then tells me it cannot find required 
� files, It does this 4 times. This PC used to have a trial version of office 
� installed but no longer has. How to stop it doing this?
� 2. A full install of MSDN was done a few times, MSDN is missing those links 
� at the top of the help file pages. Things like 'See Also, Properties, 
� Methods, Events, Applies to'. Where have my links gone?

Probably one of the Add-Ins entries that is causing this problem. Click on Add-Ins...Add-In Manager
and un check the Load on Startup option for anything related to Microsoft Office (such as Microsoft
Visio UML Visual Basic Addin).


Paul
~~~~
Microsoft MVP (Visual Basic)

"Mike Williams" <Mike@WhiskyAndCoke.com> wrote in message 
news:O2fg2cZsKHA.3408@TK2MSFTNGP06.phx.gbl...
> "MikeD" <nobody@nowhere.edu> wrote in message 
> news:%23btNKCZsKHA.4752@TK2MSFTNGP04.phx.gbl...
>
>>> "Ivar" <ivar.ekstrome000r@ntlworld.com> wrote in message 
>>> news:#5ZYvfXsKHA.732@TK2MSFTNGP06.phx.gbl...
>>> Have installed VB6 and MSDN on to my new laptop,
>>> It's Winders 7 64bit.
>>
>> First, *please* quit calling Windows "Winders". That's just juvenile.
>
> Is it okay if I continue to call it Windoze?
>

Well I can't stop anybody from calling it whatever they want, but IMO that's 
even more juvenile, but at least in some cases it's justified.  <g>

I just don't see the point in using such "nicknames".

-- 
Mike
 

Thanks for the reply, but nope, no difference at all.

Ivar 

On Fri, 19 Feb 2010 11:18:08 -0800, Karl E. Peterson <karl@exmvps.org>
wrote:

>Mike Williams wrote:
>> "MikeD" <nobody@nowhere.edu> wrote in message 
>> news:%23btNKCZsKHA.4752@TK2MSFTNGP04.phx.gbl...
>>
>>>> "Ivar" <ivar.ekstrome000r@ntlworld.com> wrote in message 
>>>> news:#5ZYvfXsKHA.732@TK2MSFTNGP06.phx.gbl...
>>>> Have installed VB6 and MSDN on to my new laptop,
>>>> It's Winders 7 64bit.
>>>
>>> First, *please* quit calling Windows "Winders". That's just juvenile.
>>
>> Is it okay if I continue to call it Windoze?
>
>Another recently cited variation... Weven. <eye roll>

Whinedoh ...

On 19/02/2010 15:26, Ivar wrote:
> Hi All
>
> Have installed VB6 and MSDN on to my new laptop, It's Winders 7 64bit. I
> got 2 problems (amongst others):
> 1. Each time VB6 starts I get a box saying Please wait while winders
> configures micro$oft office 2007. It then tells me it cannot find
> required files, It does this 4 times. This PC used to have a trial
> version of office installed but no longer has. How to stop it doing this?

Look for MSIZap.
Some part of the windows installer database has broken.
You'll most likely find some part of office still listed.

> 2. A full install of MSDN was done a few times, MSDN is missing those
> links at the top of the help file pages. Things like 'See Also,
> Properties, Methods, Events, Applies to'. Where have my links gone?

Sounds like the help system itself is broken as these are special COM 
objects.
I'm not sure what to suggest about these though.

-- 
Dee Earley (dee.earley@icode.co.uk)
i-Catcher Development Team

iCode Systems