Problem with VB controls

Printable View

Feb 25th, 2003, 07:52 AM
Rayder

Problem with VB controls

Hi All,
On our Windows 2000 machine we have various different people using the machine so we have restricted access to the computer.
Initially in VB the people could run VB and add any control they wanted, but then this happens every couple of months. The user tries to add come controls to their project and VB shuts down immediately. This also happens if they try to open up a VB project with these controls in it. To resolve the problem in the past we log in as adminsitrator and load all the controls and then exit....this seems to work fine but is very time consuming.
I'm sure that other people have ran into this problem, I'm just wonderin is there any resolution to it.
BTW we are running VB6 and SP5, sitting on Windows 2000 with SP3.

Thanks in advance,
R.
Mar 9th, 2003, 04:03 PM
usamaalam

I faced the same problem and I think this is the only solution.
Mar 13th, 2003, 11:42 PM
wrack

Re: Problem with VB controls

Quote:

Originally posted by Rayder
Hi All,
On our Windows 2000 machine we have various different people using the machine so we have restricted access to the computer.
Initially in VB the people could run VB and add any control they wanted, but then this happens every couple of months. The user tries to add come controls to their project and VB shuts down immediately. This also happens if they try to open up a VB project with these controls in it. To resolve the problem in the past we log in as adminsitrator and load all the controls and then exit....this seems to work fine but is very time consuming.
I'm sure that other people have ran into this problem, I'm just wonderin is there any resolution to it.
BTW we are running VB6 and SP5, sitting on Windows 2000 with SP3.

Thanks in advance,
R.

before you assign a user profile to users. Just log on as an administrator and start the VB and try to load controls one by one and let VB configure itself and write registry values.

Then make users and copy that user profile to them and then so forth and so on.

Its bcos u have restricted them to certain level where they can not make changes to registry and thats why when they tries to load a control first time ( for example ) it tries to set some registry values and which is restricted. So it shutdowns the VB.

Hope this helpful...

Cheers...