Knowledge Base
HOWTO: Grant Users the Access to Add Visual Basic Components
PSS ID Number: 274484
Article Last Modified on 6/11/2002
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Visual Basic Professional Edition for Windows 6.0
Microsoft Visual Basic Enterprise Edition for Windows 6.0
the operating system: Microsoft Windows 2000
the operating system: Microsoft Windows NT 4.0
--------------------------------------------------------------------------------
This article was previously published under Q274484
IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:
256986 Description of the Microsoft Windows Registry
SUMMARY
When Visual Basic 6.0 is installed by an administrator on either Windows NT
4.0 or Windows 2000, generic users can run the Visual Basic application.
However, if they try to add Components from the Project menu drop-down list
box, they receive the following error message:
Access Denied
This article demonstrates how to grant users access to add components
without giving them Administrator or Power User rights.
MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
To grant user access, create a new group of users.
In Windows 2000, the steps are:
On the Start menu, point to Programs, point to Administrative Tools, and
then click Computer Management.
To expand the branches, click the plus symbol (+) next to System Tools under
the Tree tab, and then click the plus symbol (+) next to Local Users and
Groups.
Right-click the Groups folder to view the shortcut menu. Click the New Group
menu to view the New Group dialog box.
Give the new group a Group Name, such as VB Programmers, a description, and
then add one or more Members. Click Create to save the new group.
NOTE: In Windows NT 4.0, use User Manager for Domains.
After you finish the preceding steps, modify the registry. Modify the
permissions on the following keys and add VB Programmers to these keys with
full control inheriting the permissions down the key as follows:
Start Registry Editor (Regedt32.exe).
Locate the following keys in the registry:
HKEY_CLASSES_ROOT\TypeLib
HKEY_CLASSES_ROOT\Interface
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Visual Basic
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio
For each key, click Permissions on the Security menu. Add the VB Programmers
group to the key, and then click Apply.
Select the new VB Programmers group, and then select the Allow Full Control
check box. Click Allow inheritable permissions from parent to propagate to
this object. NOTE: On Windows NT 4.0, click Replace permission on existing
sub keys.
Click Apply, and then click OK.
Quit Registry Editor.
Keywords: kbDSupport kbhowto KB274484
Technology: kbAudDeveloper kbOSWin2000 kbOSWinNT400 kbOSWinNTSearch
kbOSWinSearch kbVB600 kbVB600Search kbVBSearch kbZNotKeyword2 kbZNotKeyword6
--
Randy Birch
MVP Visual Basic
http://www.mvps.org/vbnet/
Please respond only to the newsgroups so all can benefit.
"Manitoba98" <manitoba98xp@hotmail.com> wrote in message
news:pwapb.108406$7B1.55676@news04.bloor.is.net.ca ble.rogers.com...
: I have been having trouble with controls in VB5 every since I got XP. I
am
: not the administrator, and thus I cannot use OCXs or DLLs (except for API
: Calls, which work). When I try to add a new control or set of controls to
: the toolbar, I check them, click OK or Apply, and I get an error saying
that
: VB was forced to quit. This will make it impossible for me to do work with
: WinSocks or ComDlg32, etc. This also means I cannot run applications made
in
: VB that use them. Unless I can find a way to fix this, or API calls using
: WinSocks, etc, this will seriously hinder my programming capacity in
Visual
: Basic (which is just a hobby at the moment).
:
: Manitoba98
:
:
