>>>>Is there a third party utility product that grabs the user id from a Novell network? OR, is there a way to do this within VFP 6.0? [We want to do this rather than asking users to enter a user name/password when they access our system.]
>>>
>>>GPLIB and NetLib both have functions for this. I think the need for third party tools may have gone away with VFP 6.0, but others will have to expand on that. :)
>>>
>>>HTH,
>>>Rich.
>>
>>There are a few ways to do it. 1 way and perhaps the easiest:
>>In the system login script issue the following command: DOS SET USER="%LOGIN_NAME". This will create an environment variable "user" = the user login name.
>>To get it in your code: m.user=Upper(GETENV("user"))
>>You can also do it by setting an environment variable in each work station but this can get nasty if you have a lot of machines! This works in VFP6.0 and earlier. Doesn't require a net library either.
>>S
>
>These methods are pretty much only dependable if you're part of an in-house IT department with control over the corporate network, as opposed to developing an app to be used at many locations with their own network admins. I don't know which situation Doug(? original poster) is in, but that may be an important point.
>
>Even when you're part of the in-house IT department, I've come into situations where there were the programmers (who have come and gone) and the network admins (who were also coming and going), and programmers developed various apps over the past 10-15 years which depended on (DOS) environment variables being set by login scripts, and network admins changed login scripts after these programmers were gone and programs broke and people couldn't figure out why. My point is, it's better to rely on some way of retreiving the value from the OS or Network OS itself, than relying on network admins not diddling with what you needed in their login scripts. Which means API calls or third-party libraries such as GPLIB or NetLib the last I knew.
>
>Just my opinion, which could be wrong! Anyway, I believe Doug found his solution in another member's suggestion of SYS(0).
>
>Regards,
>Rich.

Thanks for the pointer, Rich. As you can tell, I am an in house programmer as well as the network administrator! Anyway, it was good to learn about sys(0).