>Ah ok, as a system variable, would it be easy for someone to amend though?

Yes. You have to decide whether there is a risk that warrants better protection. But with a little cunning you can conceal both the purpose and meaning of any settings. The only real risk then is of an operator copying the file from one machine to another. But if they have access to the other machine in the first place then this is problematic.

On the plus side you (or 'supervisor') can change the selection of operations that a machine is allowed to perform without modifying the VFP EXE.

>
>>Why not just use an INI file setting on each machine ?
>>
>>>Thanks for that, I was hoping to just pick a machine name or whatever, it needs to be guided by the actual physical machine IE one machine in CANNING is able to CAN TAB, a mching in weighing is able to amend WEIGHTING TAB.
>>>
>>>>>I have an application where I want to grant access to certain menu options depending on which machine it is on a network.
>>>>>
>>>>>Whats the best way to achieve this?
>>>>>
>>>>>I want a supervisor to be able to say MACHINE X in CANNING has access to the CANNING TAB for example or
>>>>>machine Y is an administrator in the office so has full access to all of the programs.
>>>>>
>>>>>Is the easiest way to detect the current users login name?
>>>>
>>>>You've got answers to that - but if you want a 'supervisor' to control this externally you should maybe assign rights to windows *groups* and let the supervisor control which users belong to a specific group. Would be a doddle in .NET but I'm not sure how you would do this in VFP beyond the fact that you'd need the WINAPI CheckMembershipToken function....
>>>>
>>>>UPDATE: Found this from Sergey: http://www.berezniker.com/content/pages/visual-foxpro/-user-member-administrators-group
>>>>but it's working with a built-in role whereas you would need to specify the role.....