Use ADE R-code Location (-baseADE) to specify where the client should look for another version of ADE r-code on the same machine at the same time.

Operating system and syntax UNIX / Windows -baseADE directory
Use with Maximum value Minimum value Single-user default Multi-user default
Client Session — — — —
directory
Identifies where the client should look for the ADE r-code.

You can have different versions of ADE r-code on the same machine at the same time. As a result, you need a way to specify the ADE r-code directory to the client so that the client can add this directory and all of the libraries contained in the directory to the PROPATH. The -baseADE startup parameter lets you specify the location of the ADE r-code directory.

At session startup, OpenEdge automatically adds $DLC/gui (or $DLC/tty for character mode clients) and all libraries in $DLC/gui (or $DLC/tty) to PROPATH.

When you specify -baseADE, the $DLC/gui (or $DLC/tty) directory and the libraries in $DLC/gui (or $DLC/tty) are not added to PROPATH. Instead, the directory specified using the -baseADE startup parameter is added to PROPATH followed by all of the libraries in the directory. For example, if you use -baseADE to specify the following: 

-baseADE c:\maint\gui

And c:\maint\gui contains the procedure libraries adecomm.pl, adeuib.pl, and protools.pl, then PROPATH looks like the following: 

...,c:\maint\gui,c:\maint\gui\adecomm.pl,c:\maint\gui\adeuib.pl,c:\maint\gui\protools.pl,...

If $DLC/gui (or $DLC/tty) or any of the libraries from the directory already are part of PROPATH (environment variable, .ini file, or registry setting), OpenEdge does not remove them.

OpenEdge allows you to specify an empty string for <directory>, -baseADE "". In this situation, OpenEdge does not add $DLC/gui (or $DLC/tty) or the libraries in $DLC/gui (or $DLC/tty) to PROPATH.

You also can specify the ADE R-code Location with the BASE-ADE attribute of the SESSION system handle. For more information about this SESSION attribute, see ABL Reference.