Hi Carlos,

I did find a solution and it involved altering the package so that build include 
the Windows installer bootstrap loader.  This is a known issue with Visual Studio 
Installer.

While in VS Installer, go to Project -> Properties.  One of the settings on the "Build" 
tab is "Build Type"  If you select "Installer with Windows Installer Loader" then 
it will include the bootstrap.  This will result in a "setup.exe" being in addition 
to the "msi" file.

Now you should see the Installer load the first time for each new user, but the application 
should run properly regardless of user intervention.

Also, try checking your project for any unnecessary references or components.  I 
had poor Windows so confused at one point that it was kicking off the Office Installer 
anytime I tried to edit a form in VB....don't ask me how that happened, but it stopped 
after I rebooted!

I never did find a useful solution to updating HKCU for any and all users.  I believe 
there is a command which will allow registry updates regardless of local policy, 
but I am not in a position to override existing policy.

I should add one caveat that I ended up replacing the DataGrid which was causing 
me so many headaches with a Hierarchical FlexGrid, as the DG seemed to come with 
a set of built-in problems.

Let me know if this works for you.

Cheers,
John






On Wednesday, April 6, 2005 at 6:44 am, Carlos Lopes wrote:

>Hi John,

>I have a similar problem. A VB6 form with just a ListView control and nothing else 

>triggers the Office Install when loaded. This problem doesn't happen if I login 
as 

>administrator but it does happen if I login as a regular user who belongs to the 

>Power Users group (Win XP SP2). If you find a solution other than editing HKCU, 
please 

>let me know (lopes@intersystems.com). I'll do the same.

>Thanks,

>Carlos

>

>

>

> 

• Reply or follow-up to this message

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum