Creating a Branded Version of Stonefield Query

You can create a private labelled or branded version of Stonefield Query by changing a number of configuration settings. This allows you to distribute Stonefield Query as your own branded product, so your end-users won't know it's Stonefield Query from Stonefield Software; they'll think it's something you've created just for them. This also allows you to sell your branded version for whatever price fits your business model.

It's possible the end-user may still determine that the reporting tool is actually Stonefield Query by the names of some files, such as SFQUERY.EXE and SQUPDATE.EXE. If you want to create a branded version of the Stonefield Query files, do the following:

Start the Configuration Utility, create a project in the desired folder, and then exit.
Rename SFQUERY.INI to something else (for example, ANON.INI; this name will be used in the rest of this help topic for illustrative purposes only).
Create a text file named SFQUERY.INI in the project directory with the following content:
```
[Files]
RealINI=anon.ini
```
This file is needed only for the Configuration Utility and should not be distributed to your end-users.
Replace the names of REPMETA.DBF and SFSCRIPT.DBF in ANON.INI with the desired names; for example:
```
[Meta Data]
file1=anonmeta.dbf

[Scripting]
file1=anonscript.dbf
```
You can then delete REPMETA.DBF, REPMETA.CDX, REPMETA.FPT, SFSCRIPT.DBF, SFSCRIPT.CDX, and SFSCRIPT.FPT if they are empty (that is, this is a new project) or rename them to the desired names if this is an existing project.
Add the following to ANON.INI to replace the names of SFCONFIG.DBF, SFCONFIG.CDX, and SFCONFIG.FPT:
```
[Configuration]
file=anonconfig.dbf
```
You can then delete SFCONFIG.DBF, SFCONFIG.CDX, and SFCONFIG.FPT if this is a new project or rename them to the desired names if this is an existing project.
Add the following to ANON.INI, specifying the desired names for:
- common functions files, replacing COMMFUNC.DBF and COMMFUNC.FPT
- Advanced Report Designer, replacing SQDESIGNER.EXE
- Preview window, replacing SQPREVIEW.EXE
- output application, replacing SQOUTPUT.EXE
- IntelliSense application, replacing SQCODE.EXE, SQCODE.DBF, and SQCODE.FPT
- update application, replacing SQUPDATE.EXE
Note that these files are not actually renamed on your system; these settings specify what your custom installer should rename files to when it installs them on the end-user's system and tells Stonefield Query the names of the files to use rather than the originals.
```
[Files]
CommonFunctions=anonfunc.dbf
AdvancedDesigner=anondesigner.exe
AdvancedPreview=anonpreview.exe
AdvancedOutput=anonoutput.exe
IntelliSense=anoncode.exe
Update=anonupdate.exe
```
Use the Configuration Utility as you normally would to create your customized version. You'll likely want to specify different values for the following configuration properties:
Use the Generate Setup function to generate the installer for your custom version.
When the installer runs on the end-user's system, it will install SFQUERY.EXE, SFQUERY.CHM, SQRESOURCE.DBF, SQRESOURCE.CDX, and SQRESOURCE.FPT as files with the same root name as your renamed INI (for example, ANON.EXE, ANON.CHM, ANON.DBF, ANON.CDX, and ANON.FPT) as well as renaming the files mentioned earlier to the names specified in the INI. Also, the license file generated when the end-user activates Stonefield Query has the same root name as the INI (for example, ANON.LIC).
Test the installer on another system to ensure all files are renamed correctly and that your customized Stonefield Query works as expected.
The Stonefield Query executable (SFQuery.EXE) and update application (SQUpdate.EXE) are digitally signed so users don't get an "unknown application" dialog when they run these applications over a network. This digital signature contains our conpany name, so contact us to get unsigned copies of SFQuery.EXE and SQUpdate.EXE you can deploy instead.