INFO: Differences between Private and Public Database Names

The information in this article applies to:

• Acceler8DB, Release 4.6 and Higher
• Windows
• Deploy

SUMMARY:

This article provides information on what the differences are between Private and Public Database Names.

STATUS:

Current.

MORE INFORMATION:

NOTE:  We recommend that you run thorough tests to determine which type of database name that meet your requirements.  Please coordinate with your Network or System Administrator while working with Windows and determining levels of security.

Descriptions of Private and Public Database Names:

• Private Database names can only "seen" by the currently logged on user on Windows NT, 2000, and XP (Home and Professional Edition).  There are no Private database names on a Windows 9x machine, unless the option to keep separate profiles is selected.  The net result of database names on a Windows 95 / 98 machine will be similar to a Public database name, except there will be no "*Public/" prefix.

An example of a Private Database name is: "ASNA Local DB".

These database names are registered in the HKEY_CURRENT_USER section.

• Public Database names can be "seen" by everyone on the Local Machine.  A public database name is similar to a private database name, except it is prefixed with "*Public/" (without the quotes).  A public database name is not "secure"; in that, it can be accessed by anyone that has access to the machine where the database name exists.  Some deployed environments may require the use of Public database names.

  An example of a Public Database name is: "*Public/ASNA Local DB".

  These database names are registered in the HKEY_LOCAL_MACHINE section.

NOTE:  If you don't want to create a database name for each user, then we recommend using a Public database name.

Defining a Database Name:

A Database Name is defined in two different locations:

• In your AVR Applications F-Spec or DclDiskFile's DB or DBDesc;
• Naming a Database on the computer.

Determining which Database Name is currently in use:

1. Login with your user account
2. Open the Database Manager
3. Select Database Open from the Database Menu
4. Make a mental note of the database names listed
5. Close all applications and Logoff
6. Login with a different user account 
7. Repeat steps 2 and 3
8. Results:

   If you don't see any database names, then the database name is private.

   If you do see any database names, then read the descriptions of the two types of database names to determine which type of database name is currently in use.

Recommendations:

Note:  The items below are recommendations only.  These recommendations may not suite everyone's requirements. Testing is recommended to determine which type of database name is required for your specific need.

• Web Applications:

  We recommend Web applications to use Public database names because they are usually run out of process and under a different user than the one currently logged in.

   

• Windows Applications:

  We recommend Windows Applications to use Private database names; unless, deployment and / or maintenance requirements need to use Public database names.

Other ASNA KB Articles:

• HOWTO: Securing an Acceler8DB Public Database Name
• PROBLEM: Can't find Database Name when running within an ASP in a Web application
• HOWTO: Using multiple databases from one Web App
• INFO: Deploying an AVR Application on Citrix Server
• Securing your Database

Other MS KB Articles:

• Enabling User Profiles in Windows 9x (look for the section called: "Enabling User Profiles")

Keywords: "database name types", deployment, maintenance