Kbase P26859: 4GL/ABL: How to have distinctly different PROPATHs for different users?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/7/2009 |
|
Status: Verified
GOAL:
4GL/ABL: How to have distinctly different PROPATH for different users?
GOAL:
How to specify a custom session PROPATH?
GOAL:
How can the PROPATH of a 4GL/ABL session be modified?
FACT(s) (Environment):
Progress 8.x
Progress 9.x
OpenEdge 10.x
Windows
FIX:
In windows Operating Systems, Progress reads the PROPATH from the Windows Registry in the following order, and will use the first entries it finds for a particular version:
First) HKEY_CURRENT_USER\Software\PSC\<version>\<Startup or WinChar Startup>
Second) HKEY_LOCAL_MACHINE\Software\PSC\<version><Startup or WinChar Startup>
If Progress doesn't find the necessary Startup keys (GUI clients use Startup and Character clients use WinChar Startup) then it will find the progress.ini file in the DLC\bin directory.
In some deployment environments it is desirable to have different PROPATH for different users. For Windows users, it is possible to specify the PROPATH for a given user by modifying the Windows Registry for that user's machine or by creating a customer .ini file and a custom icon for that that user.
By modifying the PROPATH key in either the Windows Registry or in a session's .ini file, it is possible to have distinctly different PROPATH for different users.
You can override the 4GL/ABL default startup startup behavior by using the -basekey startup parameter on the command line or the icon's target line. For example the command:
prowin32 -basekey INI -ininame c:\temp\my.ini
Will cause Progress to look directly in the my.ini file for its startup information (which includes PROPATH, fonts, and other session and environmental settings).