Initialization path

You can use this field to change the initialization path for PowerBuilder.
However, be sure to copy all INI, property, and license files from
the original initialization path to the path that you enter. By
default, the initialization path is either c:documents
and settingsuserNamelocal settingsapplication
datasybasepowerbuilder 15.0 (Windows
XP and Windows 2003) or c:usersuserNameAppDataLocalSybasePowerBuilder 15.0 (Vista
and later), where userName is the user currently
logged in.

Prompt on Exit

Check Prompt on Exit if you want to be prompted before quitting PowerBuilder.

Just In Time Debugging

When this option is checked, you can open the Debug window
while running in normal mode by clicking the PowerBuilder icon and
clicking the Debug button on the dialog box that displays. The Debug window
also opens automatically if a system error occurs.

Automatically Clear Output Window

Clear this check-box if you want the output of new operations
to be appended to existing text in the Output window. The default
is to clear the Output window before sending output from a new operation
to the window.

Horizontal Dock Windows Dominate

You can dock the System Tree, Output, and Clip windows at
the top, bottom, left, and/or right of the PowerBuilder
MDI frame. When this box is checked, windows docked at the top and
bottom of the frame occupy the full width of the frame. When it
is cleared, windows docked at the left and right of the frame occupy
the full height of the frame.

Free Database Driver Libraries on Disconnect

Check to free libraries held in memory after PowerBuilder
disconnects from a database in the development environment. Checking
this option reduces memory use, but at the cost of performance loss
and possible problems with some database management systems associated
with the freeing and subsequent reloading of libraries. To free
libraries held in memory at run time, select the FreeDBLibraries
check-box on the General page of the application’s Properties
view in the Application painter.

Enable PBDebug Tracing

When this option is checked, PowerBuilder writes a sequential
log of the activities an application performs when you run it in
the PowerBuilder environment to a text file.

Prompt Before Overwriting PBDebug Output File

When PBDebug Tracing is on, check this box if you want PowerBuilder
to display a response window before running or debugging the application,
so that you can choose whether or not to overwrite the PBDebug log
file. The response window has three buttons:

PBDebug Output Path

Specify the name and location of the PBDebug log file. If
you leave this blank, the default will be a file called PB150.dbg in
the directory that contains the PowerBuilder executable file.

Use Windows Classic Style on XP

On the Windows XP operating system, select this box to use
the Windows Classic style instead of the Windows XP style in the
PowerBuilder development environment. You must restart PowerBuilder
to apply this setting. This option affects the display at design time
only. It is disabled on Windows operating systems other than Windows XP.

Disable Database Connection When Compiling and
Building

When PowerBuilder compiles an application that contains embedded
SQL, it connects to the database profile last used in order to check
for database access errors during the build process. For applications
that use multiple databases, this can result in spurious warnings
during the build since the embedded SQL can be validated only against
that single last-used database and not against the databases actually
used by the application. In addition, an unattended build, such
as a lengthy overnight rebuild, can stall if the database connection
cannot be made. To avoid these issues, select this check box.

Caution

Select this check box only when you want to compile without signing
on to the database. Compiling without connecting to a database prevents
the build process from checking for database errors and may therefore result
in runtime errors later.