I agree with the last poster.  I have been on two sites where they 
migrated from older O/S's to Windows2000.  In both cases, there have been 
no issues with VB and VSS, BUT ... in both cases, we had to give up and 
give the developers machine-level Admin rights.  It seems a losing cause 
to try and buttton-down a developer's machine too tightly.

If you change the rights and your problems go away, there's your answer.  
I am unaware of any success stories where developers have less than Admin 
rights.

R

> We circumvented the problem by setting up our developers as machine-
level
> adminstrators.
> 
> Grant their UserName Machine-level administrator priviledge.  Just as an
> aside, you will have the same issues when and if you go to .NET.
> 
> Good luck.
> David Adams
> ----- Original Message -----
> From: <john.beston@C...>
> To: "professional vb" <pro_vb@p...>
> Sent: Tuesday, February 19, 2002 09:11 AM
> Subject: [pro_vb] Visual Basic, Visual Source Safe, and Windows 2000
> 
> 
> > Hi there!
> > My firm is in the process of migrating from NT4 to Windows 2000, and 
we
> > have run into permissions problems with VB6 and VSS. According to
> > Microsoft's MSDN web site, some changes are needed to the registry to
> > allow Users to operate VB6, rather than logging in as an 
Administrators.
> > These changes are made via Regedt32, and are as follows:
> >   Give full control to users in the following registries:
> >   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools
> >   HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib
> >   HKEY_CLASSES_ROOT\TypeLib
> >
> > It also recommends installing Service Pack 5.
> > Having done all of the above, the problem still remains. I am unable 
to
> > add in any .ocx components(this causes VB to close down without 
warning),
> > and Source Safe is bringing up permissions errors on a project which 
was
> > created in NT4.
> >
> > Any help gratefully received.
> > John
> > ---