Moving Access databases or security files

Moving or renaming the security file

If you move the security file to another location or rename it, you must open each related database in iBase Designer to update the stored location.

What happens when you open the database depends on the location of the security file. The possibilities are:

• If there is a security file in the same folder as the database file, iBase Designer opens that file immediately, even if it is the wrong security file.

• If it is the wrong security file, an error message notifies the user that the database is not associated with the current security file.

• If there is no security file, iBase Designer displays a Security File browser for you to locate the moved security file and click Open.

An example message:

Incorrect Security File
You normally connect to this database via a different security file
(\\ SERVER\databases\my_security.ids).
Are you sure you want to connect via this security file
(\\SERVER2\databases2\my_security.ids)?

If you confirm that you want to use the new file, iBase Designer stores the location. You can close the database immediately, or continue working.

If you have other databases that are linked to this security file you can open and close them for update now, without needing to log on each time.

Moving or renaming the database file

After a database file is moved or renamed, there is no need to open an Access database in iBase Designer if the security file is in its original location.

As mentioned for moved security files, you (and users in iBase) need to confirm the location of a security file that is not in the same folder as the database file. However, keep the security file in the same folder as the databases it secures.

Note: Renaming a database file prevents any existing Analyst's Notebook charts from accessing that database.

Note: If your organization creates maps or Analyst's Notebook charts that use data from multiple iBase databases, the name of the database must be unique.

What users see

At their next use of each database, users must find the new location of the moved or renamed file.

After users open a moved database, iBase records any change of database location in the recently used (MRU) section of their File menu.

What happens in subsequent use depends on the relative positions of the database and security files:

• If the security and database files are in the same folder, users see no change from behavior before the move.

• If the security and database files are in different folders, users see a Security File browser each time that they need to log on and must locate the security file.