Preferences / Options

Many parameters can be preset and aplied upon loading a new HTML form. On Mac OS X systems it's known as Preferences, while on Microsoft Windows systems it's known as Options.

To invoke the preferences window, locate the Preferences menu on Mac OS X, or Options on Microsoft Windows.
Preferences menu on Mac OS X
Options menu on MS Windows

The preferences window has different sections described as follows:

Application

Some application parameters are set up in this panel, such as the automatic checking of new program versions. This is the best way to be updated with the last Forms To Go available version, which always gives functionality and stability improvements.

This is performed through an Internet connection. The application will request Bebosoft.com to inform about the latest release of the application. This connection does not send any personal or computer information.

In many operating systems, anti-spam or anti-spyware programs installation does not allow that programs connect to Internet unattended; therefore, if you notice that Forms To Go automatically starts and stops, then you must disable this option.

HTML Forms

This panel sets up actions to be taken upon loading the HTML form.

Submit, Reset and Image fields are generally used to invoke actions in the form and do not contain data. You can obviate these fields, In order to simplify the use of Forms To Go.

To make the HTML form more graphically attractive, some programs offer the possibility of using images such as buttons through "image" tags.

In case your HTML form contains one or more submit buttons, each one indicating a different action to the script, then you must not delete submit or image tags.

If you have a simple form with only one submit button, select these checkboxes.  This way Forms To Go does not include this type of fields.

PHP, ASP and Perl panels

In each of these panels, the parameters of these languages are preset. Such parameters are explained in each related chapter.

Script

Several parameters that are indirectly related to the script can be preset in this panel.

The location of resulting success and error pages, regardless of the method selected to show them, as well as the end-of-line used in the script. These values can always be changed for each script in their related parameters window.

One of the parameters that can only be set up through preferences is the one related to the replacement of extended characters and symbols for their equivalent HTML entity  in error messages, in case a validation fails.

In HTML pages, <> and " symbols are not displayed in the browser, since they are used in HTML tags. if you want to use them in the content of HTML pages, they must be replaced by their equivalent HTML entities: &lt; for <, &gt; for > and &quot; for ".

Upon selecting the Convert symbols < > " checkbox, the script generated by Forms To Go will automatically substitute them by their equivalent HTML entities. If you use HTML tags in validation messages; for example:

The field <b>name</b> is mandatory

then you should not select this checkbox.

The same occurs with all extended characters -i.e. any character different from A-Z and 0-9. For example, if in the validation an error message has vowels with accents:

Your address in Curaçao is required

and you want it to look good in any web browser, you must select the Convert all extended characters checkbox, in order to convert this message as follows:

Your address in Cura&ccedil;ao is required

Email and Database panels

In the email panel, parameters used for the email sent to the form owner, as well as the confirmation email are preset, provided these values can be preset in each new generated script.

The same applies for database parameters related to text files, the explanation of which is in the chapter on text-type database.

Files

In this panel, the way in which file and directory paths are going to be interpreted is set up upon creating the script. Paths can be absolute or relative.

It is important to appropriately select the path to be used for the correct functioning of the script. You may find more information on this topic in the appendix accompanying this Manual.