Progress
Client Deployment
Guide
Using a Relative Pathname
The most flexible but least efficient way to reference a procedure in an operating system file or a library is by using a relative pathname. When you reference a procedure using a relative pathname, Progress searches the PROPATH.
When you reference a procedure in either an operating system file or an unspecified library using a relative pathname, Progress searches each directory and library defined in the PROPATH until it finds the first occurrence of the procedure. For example:
When you reference a procedure in a specific library using a relative pathname, Progress searches the PROPATH until it finds the first occurrence of the library. For example:
When you reference a procedure in a specific library, you must enclose the member name in double angle brackets as shown.
The most flexible way to find procedures is to specify relative pathnames for all procedures run in your application. This allows you to put a procedure into a library for production, but maintain separate procedure and r-code files during development. In a development environment, either place the library in the PROPATH after your development directories or omit it from the PROPATH entirely. In a production environment, place the library at or near the beginning of the PROPATH to avoid long searches.
NOTE: Progress cannot find procedure files in a library; it can find only r-code files.For more information about how libraries interact with PROPATH, see the "Libraries and PROPATH" section later in this chapter. For more information about the RUN statement, see the Progress Language Reference.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |