>>>>>>>Thanks, Mark. Now, can anyone confirm for me that this works for a NetWare workstation (I only have an NT LAN available for testing.
>>>>>>
>>>>>>This is returning the login name of the Windows workstation. In most case, this is synchronized with the server. If this is the case, then, you're ok.
>>>>>>
>>>>>>For more network functions, for Netware, you may want to use GPLib. For NT, you may use Netlib.
>>>>>
>>>>>NetLib is great for FoxPro to. I have it for FoxPro 2.5 and am considering buying the upgrade to the VFP5 version.
>>>>
>>>>We have NetLib 3 (for all VFP) and have found many problems, unlike previous versions which we loved. It will not run if you are using NT on your workstations, and if you have an NT network the functions are severely limited. Since our app must be used with both networks, we are finding it very difficult to implement.
>>>>
>>>>Barbara
>>>
>>>Thanx for the info Barbara. I'll keep this in mind when deciding which way to go. Like you, I have a combination of NetWare and >NT servers and Windows95 work stations. I beleive NetLib 5 is out now. You might want to investigate the upgrade to see if it >fixes its NT shortcomings. Let me know if you do. If I see anything new regarding NetLib5 or other packages I'll pass it along.
>>
>>By far, the easiest way to achieve this without using any external libraries is to set an environment variable for the user name on login and use fox's GETENV() to retrieve the var.
>
>This point came up earlier in the thread. However, if the user name is required for security purposes then the main short coming of using an environment variable is that the user can easily change it. i.e. SET USER=SUPERVISOR

But they would STILL need to know the appropriate password.