Ridiculous? Are you kidding? This is the epitome of streamlined access of a document’s properties!!! What more could one ask for? I suppose all you want to do is ask for the document’s path and have it returned accurately! There is no fun in that, where is the challenge? :lol: Just kidding, of course. It is truly a hack around.
I have tried many many ways to get the path, and would have gone the “find” route, except there was too great a chance that I may pick up the wrong file. My situation is that all of our files are on a UNIX server, and there are as many 30 volumes mounted on any of the 130 desktop machines,on which we work about 2000 Quark pages a day. It was just too cumbersome to find, and I didn’t feel certain that I would be picking up the correct file or version of that file. Educated guessing along with a find would have made it better, but not good enough. If I was working with fewer variables, then I would have went with one of the locate methods. The best thing about these forums is you normally get several solutions to a problem. Some better than others, and some just better suited than others.
Oh, and I don’t want to take credit for the script itself. This was provided for me by Quark, and while I think it was a clever workaround, I really wish that “path of document” would just return the true path of the document. Maybe it will be addressed in a patch, which will probably break all of our code anyway.
Anyway, at least I have a solution for now, and can finally move forward with my current projects.
Happy Easter everybody!
