Document Conventions

Different typefaces and type styles are used throughout this document to indicate specific information.

In this document, references to Windows include:

Windows 2000
Windows XP Professional (Pro)
Windows 2003

In this document, references to UNIX include:

AIX
Linux
SunOS (Web server components only)

All Windows dialog boxes, edit boxes, screens, and product displays in this guide are shown in Windows 2000. Some features and options may not be available or may be accessed differently on other Windows systems.

NOTE	Although the database account containing the FlashConnect software may be named differently for your installation, this document usually refers to it as the WWW account.

Syntax Conventions

Convention	Description
Courier New	Indicates code examples, syntax, commands, options, and other keywords recognized by the system.
Courier New bold	Type words or characters in Courier New bold at the TCL prompt. These boldface words are commands, file names, options, and other keywords recognized by the system.
Italic	Variables to be replaced by the value. It can be an actual name, word, or number. For example, file.name might be replaced with CUST.FILE. Non-linked references to other documents and topics. Emphasis for impact or the first time a word is used. For example, …resources and information make up the state of the application.
n{-m}	The letters n and m represent numbers. Numbers are usually input as a single string without commas. Numbers can also be used to define a range designation. The starting and ending numbers are typed with a hyphen between. For example, n{-m} could be replaced by 10 or by 1-31.
{ }	Braces ( { } ) delimit a mutually exclusive set of options.
on \| off	The vertical line or pipe sign ( \| ) separates a mutually exclusive set of options.
[0 \| line \| ?]	Brackets ( [ ] ) indicate optional entries.

File Naming Conventions

The w3... file names (w3Exec, w3HtmlInsert, and so on) use capitalization to make them easier to read in the text. The casing is not necessary when typing them in your applications.

If your database is case sensitive, all constants must be in uppercase although mixed cases may be used in our examples.