Multi Database
236
To obtain an empty Multi central database, either:
• For an MS-Access compatible format, see
To Create an Empty, MS-Access-Compatible Multi
Db,
below
• For a SQL-Server compatible format, see
SQL-Server Template, p. 237.
Following log on to Admin
The next time that you use Admin, the same Multi db is used.
And what about the Local Db?
When users run View, a partial copy of the Multi db (Local db) is made to that PC’s hard drive.
Tip
Creating a Multi db is a rare occurrence.
Though you can create another Multi db at any Admin log on, there is no need to do so. The
Multi db name is usually left unchanged during regular use of Admin. Only one Multi db is
needed for all of the Rapid Eye sites in your system.
Naming Restriction
Multi db naming restriction
When choosing a name for your Multi db, there are restrictions. Do not use:
• A user name. Names that you will need for a user of the Multi db. A Multi db with the same
name as a user account causes an error when View is started.
• “Administrator”. It is the name of the default user in any Multi db.
User naming restriction
When adding users to the database, do not use the “[database name]” as a user name. A user
account with the same name as the database causes an error if a copy of the database is made
locally. For other
Naming Restrictions, see p. 156.
To Create an Empty, MS-Access-Compatible Multi Db
You do not need a copy of Microsoft Access to use this procedure. Everything is included with
your copy of Rapid Eye Multi software.
1. Start Admin. The procedure to do so is on p.
232, in the Starting Admin section.
2. In the Admin Logon window, leave or type “Administrator” in the User ID box.
3. Leave the Password box empty. An empty database lists one default user: “Administrator”.
By default, this user has no password. There is more information about the default user in
section Administrator Password on p. 176.
4. Leave the Multi Central database to “Microsoft Access”.
5. First-time logons can proceed as is. Either:
• First run. You have the option of naming the database and selecting its path.
• Subsequent runs. Change the name of the database file. This instructs the
database tool to create an empty database bearing the name that you typed.