|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Thanks Vernon, <Rod You don't want to do anything hard, do you? :-) not if its been done before . . . :) <Does the qp0lGetAttributes() return full path as one of the options? It <_does_ return a file ID, from which the full path is available with <qp0lGetPathFromFileID(). spot on, this should solve the absolute path issue <Seems that QShell special attributes would not be needed outside of QShell. I wasn't worried about QShell. I just included it for completeness re different path rules. <Pathname rules are loosely (?) based on Unix characteristics, seems to me. . . . . <Does IFS Concepts have the best description of the rules? I'm not sure. There are references to Path rules in different places of the info centre. You have to dig deep. Suffice to say I found it a little imprecise. There certainly is an "unormalised" path (command parameter) and a "normalised" path (api parameter). If I can't find an api to do this normalisation I'll have to write one. Anyway, when I get this all sorted out I'll post it as commands or procedures usable from CL. Rod Orr ********************************************************************** This email may be confidential and/or privileged. Only the intended recipient may access or use it. Any dissemination, distribution or copying of this email is strictly prohibited. If you are not the intended recipient please notify us immediately by return email and then erase the email. We use virus scanning software but exclude all liability for viruses or similar in any attachment or message...,..,..,. **********************************************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.