Ed-

I found it really hard to sort the technical information from the non-technical in your post, but I've done my best. As I usually try to do.

> GETFILE() isn't up to lots of tasks I'd like it to do.

No doubt. Nor for me. But, it seems nearly adequate for the poster's needs. At least AFAICT.

> If this is one of those cases (and the description of the problem you give tells me it just might be)

Uh, it's not my problem, so all you have from _me_ is my, perhaps, incorrect understanding of the original poster's question.

>FULLPATH(CURDIR()) is a better version of SYS(5)+SYS(2003),

Point taken.

> and you've gone and made a horrid mistake, here, fishlady - you've gone and a$$umed that the current directory is the application directory!!!

Yep. Correct enough. But, then CURDIR() has that same problem, no?

> GETFILE() can be used with FULLPATH() and then tested with FULLPATH(Blah, blah, stupid directory) to make sure the idiot end-user didn't make use of the power handed to them by the immensely lazy programmer who was lacking in neurochemical energy expenditure when they decided that GETFILE() was just the ticket. It was - a clear ticket to an invite to off.ramp if they really want to know what I think of the bad habit of using GETFILE() incorrectly...I can't use the requisite vocabulary here.

The point that I'm sure you are trying to make in this paragraph is being utterly lost to me. But, it's only important if it helps the originator of the post.