A Stonefield Query project consists of the following files:

• SFQuery.INI: this is the main project file. It tells Stonefield Query which data dictionary and script files are used by this project. A project can use more than one set of data dictionary and script files; for example, you may have a project that combines the data dictionary and script files of two applications, such as an accounting application and a contact management system. Here's an example of what this file looks like:

  [Meta Data]
  file1=repmeta.dbf
  
  [Scripting]
  file1=sfscript.dbf
  
  [Encryption]
  Password=gdh#&$#^%$

  If more than one set of data dictionary or script files is used, other lines appear under the appropriate sections (for example, "file2=gmmeta.dbf" to specify a second set of data dictionary files).

  If more than one data dictionary is listed in SFQuery.INI, the last one listed is the one new data dictionary records are added to. Updates to existing items are written to the file the record is stored in. This allows you to distribute a "standard" data dictionary but allow your users to purchase their own copy of the Stonefield Query SDK and use the Configuration Utility to add custom tables and fields. The same is true if more than one script file is specified.

  For example, suppose you want your users to customize the data dictionary themselves, adding new tables and fields. Add "file2=custommeta.dbf" to the [Meta Data] section of the SFQuery.INI file you distribute with your customized Stonefield Query application. When the user uses the Configuration Utility to customize the data dictionary, changes to existing records are written to REPMETA.DBF but new records (such as new tables and fields) are written to CUSTOMMETA.DBF instead. You do not have to create or distribute CUSTOMMETA.DBF; that happens automatically when the user opens the project for the first time in the Configuration Utility.

  The Encryption section may not appear if the project isn't encrypted.

  If you want Stonefield Query and the Configuration Utility to load certain libraries (FLL files) into memory when a project is opened, specify them (with the full path) in a [Libraries] section. For example:

  [Libraries]
  file1=c:\program files\phdbase\phdbase.fll

  This file is created when you use the New Stonefield Query Project button in the Configuration Utility, is updated when you use the Project Encryption function in the Configuration Utility, and is the file name you pass to the Stonefield Query executable (SFQuery.EXE) so it knows which set of configuration files to use.

• SFConfig.DBF, FPT, and CDX: this set of files contains the configuration settings for the project. There is only one set of these files for a project, so they aren't listed in SFQuery.INI as the other files are. These files are created when you create a new project in the Configuration Utility and are encrypted if you encrypt the project.

• SFScript.DBF, FPT, and CDX: this set of files contains the script code for the project. Since you may have more than one set of scripts for a project, the name of each file is listed in SFQuery.INI. These files are created when you create a new project in the Configuration Utility and are encrypted if you encrypt the project.

• RepMeta.DBF, FPT, and CDX: this set of files contains the data dictionary, or meta data, for the project. Since you may have more than one set of data dictionary files for a project, the name of each file is listed in SFQuery.INI. These files are created when you create a new project in the Configuration Utility and are encrypted if you encrypt the project.
  

Do not change the contents of any of these files directly; they are created and maintained by the Configuration Utility.