>>If the user doesn't have rights to a directory, at least on Novell, they can't see it. IOW, it's as if the directory doesn't exist. I don't know if this helps or not.
>
>Hi Geo!
>
>that's what I was getting at... FILE() should work just fine, especially if you use UNC instead of counting on local drive mappings that can get trashed over time.

Thank you both for sharing my headache :)

Ooops, I should have given more detail. The trouble is, this is a suite of apps, so some modules may be using some common tables which reside in other app's directory (namely, its data subdirectory), and it's got so many such connections we simply have to give them rights to see it all, because nobody knows what would break if we don't (now don't mention documentation etc, we have it, but just searching through it would take too long). Therefore I'd like to just have specific execute rights set or revoked, so they'd not be able to run certain modules, and yet be able to open their tables.

Now how do I know if the current user has execute rights on a certain executable? Or should we just set the read rights to executable itself... nope, what if we upload a new one, we usually rename the old one, what happens to the rights then? I'd rather go for execute rights on the entire directory.