>>A technique that I used (a long time ago in 2.5/dos) to find if a user had sufficient rights to do something to a file was as follows...
>>
>>Try and rename the file to itself
>>

Rename filename.exe to filename.exe

>>If the user does not have NW rights an error is reported
>>If the user has rights then a different error is reported (something like cannot rename to the same name)
>>
>>You need to have a localised error trapping routine for this but it does work (all this was on a Novell N/W but It may work in the same way)
>
>This sounds really interesting and looks like one of those neat VFP tricks. I figure the error reported would depend on the operating system involved, but since we'd have to cover only one, it'd be an option. Actually, it's the best plan B I've got so far - plan A would be a separate level-2 launcher in a subdirectory, one per application, so that the IT folks there would be able to set up the rights at this subdirectory level, and then the level-1 launcher would just check for the visibility of level-2 launchers.

Dragan,

Which technique did you use in the end?
Just interested to see if my suggestion still works the way it used to.