VB6 and office components  
Author Message
jtstoudt





PostPosted: Wed Apr 25 11:55:12 CDT 2007 Top

Visual Basic >> VB6 and office components

My Application is written in VB6.
When the local user is setup with privileges of Admin user every thing is OK,
Only when the local user works with a downgraded privileges access he gets
message on updating MS Office Configuration(winddows installer is runnig)
every time the end-user application launches (opens).

This message appears several times (4-6 times) and you have to press the
Cancel key in order to move between messages until the programm comes up and
then you can with the program as usual.

This application uses several Microsoft components :
Microsoft Rich TextBox control
Microsoft Windows Common Controls
Microsoft FlexGrid Control
Microsoft Common Dialog Control

We opened MS Office applications but everything run OK.

Anybody knows what is problem?

Visual Studio86  
 
 
Ralph





PostPosted: Wed Apr 25 11:55:12 CDT 2007 Top

Visual Basic >> VB6 and office components


> My Application is written in VB6.
> When the local user is setup with privileges of Admin user every thing is
OK,
> Only when the local user works with a downgraded privileges access he gets
> message on updating MS Office Configuration(winddows installer is runnig)
> every time the end-user application launches (opens).
>
> This message appears several times (4-6 times) and you have to press the
> Cancel key in order to move between messages until the programm comes up
and
> then you can with the program as usual.
>
> This application uses several Microsoft components :
> Microsoft Rich TextBox control
> Microsoft Windows Common Controls
> Microsoft FlexGrid Control
> Microsoft Common Dialog Control
>
> We opened MS Office applications but everything run OK.
>
> Anybody knows what is problem?
>

This problem has several causes, but essentially it comes down to either a
'partial' install, an erronous flag left behind, or failure of the
administrator install to install for "all users". It sounds like the later
is most likely. Actually for many Office products a separate Admin and User
install is needed.

The simplest solution is to not cancel and let the installer do a
'user-install'.

For a permanent repair you will just have to test and find out what is not
getting registered or made available and likely make adjustments to your
setup. Perhaps your intall package is installing components it doesn't have
to? Are a different date/build/etc? Lots of reasons.

-ralph


 
 
Schmidt





PostPosted: Wed Apr 25 12:11:40 CDT 2007 Top

Visual Basic >> VB6 and office components



> When the local user is setup with privileges of Admin user
> every thing is OK, Only when the local user works with a
> downgraded privileges access he gets message on updating
> MS Office Configuration(winddows installer is runnig)
> every time the end-user application launches (opens).

Seems to be a weird registry-problem (seen often
after updating Office-Installs with a service-pack).

I've seen these Dialogs popping up mostly in conjunction with
VB-PropertyBag-Usage (on reduced user-accounts).

We then replaced the PropertyBag-Usage in our Projects
with our own Implementation (using IPersistStream and
IPersistStreamInit).

But the PropertyBag doesn't seem to be the only cause,
wich provokes these annoying Office-Install-Dialogs -
but don't remember anymore, what other combinations
we've encountered over the years.

Olaf




 
 
Paul





PostPosted: Wed Apr 25 13:27:54 CDT 2007 Top

Visual Basic >> VB6 and office components

¤ My Application is written in VB6.
¤ When the local user is setup with privileges of Admin user every thing is OK,
¤ Only when the local user works with a downgraded privileges access he gets
¤ message on updating MS Office Configuration(winddows installer is runnig)
¤ every time the end-user application launches (opens).
¤
¤ This message appears several times (4-6 times) and you have to press the
¤ Cancel key in order to move between messages until the programm comes up and
¤ then you can with the program as usual.
¤
¤ This application uses several Microsoft components :
¤ Microsoft Rich TextBox control
¤ Microsoft Windows Common Controls
¤ Microsoft FlexGrid Control
¤ Microsoft Common Dialog Control
¤
¤ We opened MS Office applications but everything run OK.
¤
¤ Anybody knows what is problem?

Check the References and Components for your Visual Basic app. Make sure that you're not using any
Office components that are not required by your application.

I used have a similar problem when launching VB 6.0. Turned out is was a Visio add-in that had been
registered under another account.


Paul
~~~~
Microsoft MVP (Visual Basic)