FactSage - List of Database Files
1. Database Files stored in \FACTDATA
To locate the \FACTDATA directory on your PC, at the top of the FactSage main menu click on ‘Tools > FactSage version, directories, …’ and consult the Data directory. For most Standalone and Client Versions the databases are stored in \FactSage\FACTDATA .
In FACTDATA the data are stored as compounds (base.* files) and solutions (soln.* files). A protected public database (e.g. FToxid) may several files (e.g. FToxid53base.* where * = cdb, crf, iw0, iw1; FToxid53soln.* where * = fdb, idx, ini, iw0, iw1, rtf, sdc, sdi)
Screenshot showing the summary of public databases in FactSage 7.0.
The FACTDATA databases and indexes are protected. Do NOT edit a \FACTDATA file - this will cause the database to become corrupt and cause FactSage to go into protected (FactSage-Setup) mode. (The BINS databases can be edited using the Compound and Solution modules – it is recommended that you first copy the databases to another directory so that the original files remain in tact.)
In the FactSage main menu click on 'View Data' - this opens the View Data module. Then click on the ‘Summary’ button for a complete list and status of all the FactSage database files stored on your PC.
2. FactSage Standalone Version
For a Standalone Version (the PC has a dongle) the databases are stored in the \FACTDATA subdirectory of the FactSage installation (typically \FactSage\FACTDATA).
3. FactSage Network Version
For a Network Server Version (the Server has a password) the databases are stored in the Server\FACTDATA directory. Each time a Client PC runs FactSage it checks the Server directory to see if it has a copy of the latest databases. When necessary the databases are automatically copied from the Server and updated in his Client\FACTDATA directory. When a new or updated database is added to the Server\FACTDATA this will be copied to the Client\FACTDATA directory the next time the Client runs FactSage.
If you have a private database that you wish to share with others on the network, simply copy it to the Server\FACTDATA directory – FactSage will make sure all the clients get a copy.
4. Activating a Private Database – Adding it to the List
If a private database file is stored on your PC, in order to include it in FactSage calculations you must add it to the List of databases (i.e. tell FactSage what the database is and where it is stored). In the FactSage main menu click on 'View Data' - this opens the View Data module. Click on the ‘Summary’ button for a complete list and status of all the FactSage database files – specify the directory where your private files are stored (we recommend that you do not store private data in \FACTDATA). You will now see which databases are already on the List (see ‘OK’) and which are not but could be (see ‘>No<’).
Now click on 'Add ...' – this opens a ‘List of Databases’ Window. (In the other FactSage modules clicking on ‘Data Search > Databases …’ has the same effect.)
Two methods are offered for you to add databases to the List:
If the database is coupled (compound and solution databases with the same database nickname) you must add both databases to the List.
5. Including/Excluding Databases in Calculations
Even though a database has been activated and appears on the List, in order to include or exclude it in a calculation, for example in Equilib, Reaction, Phase Diagram and Mixture modules, click on the 'Data Search' menu bar within these modules. This opens the Data Search Window which lists all the activate databases. Click on a database checkbox in order to include or exclude that database in the data search.
6. Database Information
Extensive documentation is available for most of the databases. In the FactSage Menu Window click on the 'Documentation' button located in the Database group - this opens the FactSage browser and displays a 'tree-view' index of the database documentation.
The same database documentation may also be accessed through the internet - go to www.factsage.com and click on 'Documentation'.
Even if you do not have access to the databases you can still consult the database documentation.