>>>I've been told here in my new job with VFP that the previous programmer discovered that he could not access the "machine name" in Win95 as he had been doing in Win 3.1.
>>>This is all new territory for me, but I have to learn how to set up access levels for about 80 people, so if anyone is knowledgeable about what is possible on the network with Win95, I would appreciate some clues....
>>>Thank you, Tom Hayward
>>
>>Tom,
>>
>>If you are trying to establish security access you should be aware that the client machine name and user returned with sys(0) may not be the same user id for the Novell login. You will most likley want to use the Novell login ID for access rights and not the client machine/user name.
>>
>>Mike
>
>Good point, Mike, that is the reason why I hoped to understand this issue, so I could branch according to access level.
>So, if sys(0) could be different than the Novell login ID, then how do I get the Novell login ID with VFP 5.0 ?
>Thanks, Tom Hayward

Tom,

I have used both GPLIB and NETLIB with VFP and Novell. These are 3'rd party products. You should be able to retrieve the login ID via the API call as mentioned, but I have never used that approach. I need full access to the Novell bindery which these products provide. Drawbacks are Netlib is available for Win 3.x/95 but the NT version has yet to be released. GPLIB supports Win 3.x/95 and NT but requires the Novell Client 32 be loaded. Both support Foxpro 2.x, VFP 3.0 and 5.0. You may also download a free evaluation copy of GPLIB to check out.

As George mentioned, the machine information must first be assigned by the network software and the network shell must be loaded. The problem is that I cannot rely on the network making these assignments. If you are the Novell administrator and have complete control over the login scripts then you may be able to.

HTH,
Mike