file (called fin.bat, for example) with which the user starts the program.

Connecting Automatically

Many of the properties that are described in the this chapter can be entered as command lines after the command prompt or included as program properties that are automatically set when you start Navision.

To carry out this procedure you must have administrative rights on the computer.

To set them as automatic program properties:

1 Open Windows Explorer.

2 Open the folder Documents and Settings, All Users, Start Menu, Programs, Navision.

3 Notice that there are two identical Navision icons on the right. You must select the icon for the version of Navision that you are using.

On Windows XP and Windows 2000 you must delete the existing shortcuts and create new ones in order to gain access to the Target field. Also note that by copying the shortcut to the user specific folders, you can tailor the program properties to the individual user.

4 Click File, Properties or right-click the Navision icon and select Properties. The

Microsoft Business Solutions–Navision Properties window appears:

5 Click the Shortcut tab. The Target field shows where Navision is located. It contains the path for the start command fin.exe. After the start command, you can add other commands and settings for program properties.

Here is an example:

servername=My Server, nettype=tcp, company=CRONUS International Ltd.

When you set the program properties in this way, the program performs certain tasks the next time it is opened. It will use TCP/IP to connect to the server called My Server and open the company called CRONUS International Ltd., if it exists in the database. If you don’t enter the company parameter, you will have to open the company manually after the program starts.

You can change any of these selections while you are working. You can do this from within the program. For example, you can select a different database (provided it has already been created) or a different company, or you can create a new company. If you do not want a client to be able to do these things, you can set limits when you assign user permissions (by setting limits on the "system" object type). You can read about assigning user permissions on page 96.

The Navision database is the heart of the application. All the information, companies, modifications, reports, and so on are stored here. It is therefore important that you know how to manage the database and are familiar with the tools that Navision provides for doing this.

This chapter describes the basic operations involved in working with a database, as well as some more advanced features.

The chapter contains the following sections:

· The Standard Database

· Creating and Maintaining Databases · Testing the Database

· Deleting the Database · Database Information · Database Efficiency · License Files

· Expanding a Working Database · Advanced Database Information · Standby and Hibernation

3.1 T

S

D

You must have a database to be able to work with Navision. When you install a single- user installation, a standard database called database.fdb is automatically provided.

Using the Standard Database

You can use the standard database (database.fdb) in two ways: with a demonstration license (cronus.flf) or with your own license (fin.flf). The standard database contains a demonstration company called CRONUS International Ltd.

Using the Demonstration License File Cronus.flf

If you choose to work with the demonstration license file, cronus.flf, you have access to all the Navision application areas and can test all the functions – including ones you have not purchased permissions for. The demonstration license file does, however, contain certain restrictions:

Restrictions of Cronus.flf

· Posting is only possible in the period November to February.

· You are only allowed to make 4000 write transactions in a database. · The maximum number of companies is two.

· You can only have stand-alone installations or run Navision Database Server on Windows 2000 and Windows XP.

· You can have a maximum of two sessions running at any one time.

· Any company name must start with CRONUS (written in capital letters). This ensures that it will be clearly identifiable as a demonstration company – and you will not accidentally create a "real" company with the wrong license file.

Using Your Own License File

If you work with your own license file (fin.flf), you can use only the functions for which you have purchased permissions. This means that you can see only the data for those functions – even in the demonstration company.

On the other hand, your own license file does not limit posting dates. You can also create as many companies in database.fdb as you have purchased permissions for. If you create more than one additional company in the database, however, you will no longer be able to use the license file cronus.flf because it allows only two

companies in the database. Thus, you will lose the benefits of using cronus.flf, for example, you will not be able to see all the functions in the entire demonstration company.

3.2 C

M

D

The demonstration database contains many limitations, which can be difficult to keep track of. Therefore, we recommend that you create a separate database for your own companies. Your license file specifies the maximum size for your database, and you can create as many new companies as you like within the allowed space.

To create a new database for your companies, you must:

1 Create the new database.

2 Restore the backup of the original standard database (database.fbk) into the new database. The backup must include at least Data Common to All Companies and Application Objects. Data Common to All Companies includes the program’s report list and permissions groups. Restoring Application Objects transfers the accounting application to the database. For more information about making backups, see "Making Backups" on page 111.

. . .

Regardless of whether you choose to continue to work in the standard database or create a new one, make sure that you always have at least one copy of the database you are working with stored in a safe location. If you accidentally delete the folder containing Navision, the database file will disappear, which means that all your data

. . .