| Solution ID: prim30123 |
| What are the differences between how Primavera 4.1 and 5.0 store database connection aliases? |
| Status: Reviewed |
| Version(s): 5.0 |
| Problem: | What are the differences between how Primavera 4.1 and 5.0 store database connection aliases? |
| Problem: | How are aliases managed in Primavera 5.0? |
| Problem: | How do I remove an alias in Primavera 5.0? |
| Fix: |
Primavera 4.1 and earlier: Used Borland technology where the aliases were stored in C:\Program Files\Borland\Common Files\BDE\IDAPI32.cfg file (viewable in Borland BDE Administrator control panel), and referenced in the PM.ini file by Alias Name, public user name, password and group id. The client login window Database Name field is populated with the alias references stored in the PM.ini file. Primavera 5.0: Uses Borland DBXpress technolgy to store and manage the database aliases. The alias information is stored in Windows registry keys and in Borland DBExpress initialization files. The client login window Database Name field is populated with the alias stored in the Windows registry keys.
The registry keys reference all aliases that are created on the PC where the application resides. The keys hold the database connection Public username, password and group id information to connect to the DB. Image may be NSFW. HKEY_CURRENT_USER\Software\Primavera\Databases\[PM | MM ]\CurrentAlias stores the last alias that was used by a user to login into the client application: Image may be NSFW. From the DBExpress side instead of storing aliases in an IDAPI32.cfg, Borland DBExpress uses two INI files.
Under HKEY_LOCAL_MACHINE\SOFTWARE\BORLAND there are two registry keys that point to these two INI files that store dbExpress aliases (DBXConnections.ini) and driver information (DBXDrivers.ini). You can manually edit the DBXConnections.ini file to remove aliases. Image may be NSFW. Image may be NSFW. |
