FlexPro stores all objects that you create or import in a project database. The inner structure of a FlexPro project database resembles the file system on a hard drive. Instead of files on the hard drive, a FlexPro project database contains data sets, formulas, presentation objects, worksheets and documents that you need for your analysis. Just like on a hard drive, you can build up a hierarchy of folders in a FlexPro project database to organize your FlexPro objects.

How Project Databases are Stored

When you store a project database, you are offered two options for saving the project database. Your work with FlexPro does not depend on how you have set up your project databases. The distinction is made for purely technical reasons.

•In a single file

This is the default storage method for a new project database. All FlexPro objects are combined into one file. The advantage of this format is that it is easier to use because only a single file is set up on the hard drive. If you would like to back up your project database or transfer it to another computer, you only have to copy a single file, e.g. ProjectDatabase.fpd. One disadvantage of this format is the slightly slower access speed, especially when you are working with large amounts of data. A further disadvantage is the higher risk of data loss in the event that the inner structure of the project database file becomes corrupted, such as due to a system failure while saving the file. FlexPro can recognize and delete defective objects within the file. In rare instances, however, it may no longer be possible to read the project database.

•In several folders and files

This is an alternative storage option. In this case, the folder hierarchy which you build up in your project database is associated with folders on your hard drive. When you create the Project Database project database, in addition to the ProjectDatabase.FPD file, two subfolders called ProjectDatabase.DB and ProjectDatabase.TMP are added to the same folder. The project database folder hierarchy is stored under the ProjectDatabase.DB hard drive folder. All FlexPro objects are saved at the corresponding positions within the hierarchy as separate files. The ProjectDatabase.TMP folder is used to store temporary files and only exists while the ProjectDatabase.FPD is open.

If you want to make a backup of your project database, you will have to make a copy of the file ProjectDatabase.FPD as well as of the ProjectDatabase.DB folder.

The folder-oriented storage system is recommended when you are working with very large amounts of data. You can increase FlexPro's performance by using this type of storage. In addition, there are no limitations in this format with regard to the total size of the project database and the maximum number of folders within it.

Note:   If possible, you should not make any changes to FlexPro objects under the DB folder. All relevant operations are available in FlexPro.

Project Database Storage Options

You can determine whether calculated images of presentation objects and calculated results of formulas should be stored in the project database by setting this in the project database Properties dialog box. Elements that you store in the project database will not have to be recalculated the next time you open the project database. On the other hand, in certain circumstances considerably more space may be used on the hard drive when saving the data, particularly when saving the results of formulas.

Different Modes for Opening Project Databases

You can choose from three different modes to open a project database:

•Backup copy

When a project database is opened, a backup copy is created. All further work is done in this copy. When the work is saved, the changes to the copy are transferred to the original database. The copy is deleted when the project database is closed. Please note that you can only use this mode if you have sufficient storage space. Important: backup copies of externally stored Excel workbooks that are linked in the project database will not be created.

This is the default mode for opening project databases.

•Read-only

Use this mode to open your project database if you want to be absolutely certain that no data in the project database can be changed inadvertently. Project databases that are write-protected, such as those on a CD, are automatically opened using this mode.

•Direct

Use this mode if you would like to edit the project database directly or if you do not have enough space available to work with a backup copy. All changes are carried out directly in the project database without a request for confirmation.

Multiple users competing for access to one project database

If a user already has a project database open, additional users can work with the project database at the same time. In this case a copy of the original has to be created. The following table provides an overview of all possible scenarios:

Possible conflicts are automatically recognized, and the system asks whether a copy should be created. Please note that any changes made to the copy will have to be transferred manually to the original database once it is accessible.

Note: Project databases appearing in the list of recently used project databases in the File menu will be opened in the same mode as when they were last opened. A project database will first be closed if it is already open and is then opened again in a different mode. The system will then try to open it in the requested new mode.

Compatibility

FlexPro 2021 is backward compatible with previous versions of FlexPro, which means that you can use project databases that you created with older versions of FlexPro in FlexPro 2021. If you open this type of project database in FlexPro 2021. It is then converted to the FlexPro 2021 format and can no longer be opened in the previous version of FlexPro.

If you purchased FlexPro 2021 as an update to a FlexPro 2019 license, you can continue to use FlexPro 2019. FlexPro 2019 also runs using the FlexPro 2021 license. If you want to edit a FlexPro 2019 project database and you want to ensure that the database can continue to be read in FlexPro 2019, then you will need to edit it in FlexPro 2019.

Data Indexing

During indexing, the program runs through all of the objects in the project database and an SQL database is created, into which header data of the objects, such as names, comments, parameters or units, are included. In the case of data sets, additional statistical data such as data set sizes, maxima or mean values are calculated and stored. The index is saved in the project database file. Indexing runs in the background and the index is automatically updated when you modify or add objects. The index created in this way speeds up the search in the project database and allows flexible searching for data with the DataQuery object.

Template Databases

•Shared template databases (FlexPro Professional, Developer Suite only)
As a FlexPro Professional and/or Developer Suite user, you can set up a list of shared project databases that are usually located in network folders. These template databases are opened in FlexPro as read-only and only briefly during normal operation so that multiple users can use them at the same time. Exclusive access applies only when you use the Organizer dialog box. You cannot store macros in shared project databases. Use them to share text import schemas, analyses, unit tables and FPScript function libraries within a team.

See Also

FlexPro Main Window

HTML Export

Working with Project Databases

Creating a New Project Database

Searching through a Project Database

Saving the Workspace

Defragmenting a Project Database

Troubleshooting Project Databases

Setting Up a Shared Template Database

Setting Up Indexing of Project Databases

Setting the Save Options

Exporting Project Databases as a Web in HTML Format

Exporting a Complete Project Database

Exporting Individual Project Database Objects

Exporting Multiple Project Databases to a Single Web Document