Re: alternative to hard coding a directory location?

From: Karsten Farrell <kfarrell_at_belgariad.com>
Date: Tue, 26 Nov 2002 17:39:23 GMT
Message-ID: <flOE9.619$RO4.34767165_at_newssvr21.news.prodigy.com>


Also, on the PC where Forms/Reports is installed, you'll find the following "keys" in the registry at HKLM\SOFTWARE\ORACLE\HOMEn, where n is the home number (mine is HOME1, but yours is probably different):

FORMS60_PATH, GRAPHICS60_PATH, REPORTS60_PATH Elias Asfaw-Kirby wrote:
> We do the same type of thing:
> Open_form('filename');
>
> In windows environment set:
> FORMS60_PATH=C:\MyForms
> or what your path is.
>
> If you call a report from forms there is a REPORTS60_PATH also
>
> Elias Asfaw-Kirby
> elias at icpsr dot umich - edu
>
> --
> ---
> "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
> news:a20d28ee.0211060057.2d5ce2f9_at_posting.google.com...
>

>>mburns_at_sjm.com (Mark Burns) wrote in message

>
> news:<549bf180.0211050943.22a96c3d_at_posting.google.com>...
>
>>>I am trying to help out a coworker who is using a hard coded location
>>>to open another form with a trigger on button. She is currently using
>>>this format to call the file
>>>OPEN_FORM('W:\xxx\yyy\filename');
>>>
>>>and I would like to change this to something like
>>>
>>>OPEN_FORM($Home'filename');
>>>
>>>So that trigger calls the file that is in the same directory as the
>>>menu file that is calling it. This will help us to use source control
>>>a little more efficently.
>>>
>>>thanks
>>>Mark Burns
>>
>>
>>Using '%<ENV VAR>%/filename' should do the trick.
>>
>>Hth
>>
>>Sybrand Bakker
>>Senior Oracle DBA

>
>
>
Received on Tue Nov 26 2002 - 18:39:23 CET

Original text of this message