OJSyntax

Description

Specifies how DataWindow Designer formats the SQL syntax for outer joins for the database back end you are accessing.

Applies to

ADO.NET
Informix 9
ODBC
OLE DB
O90 Oracle9i
O10 Oracle 10g

Syntax

OJSyntax = value

Parameter	Description
value	Specifies how you want SQL syntax to be formatted. Values are: ANSI_Escape Apply ANSI standards and enclose the outer joins in escape notation { oj ... } that is parsed by the driver and replaced with DBMS-specific grammar. ANSI Apply ANSI standards. PB Maintain rules that applied to PowerBuilder 7.

Parameter

Description

value

Specifies how you want SQL syntax to be formatted. Values are:

ANSI_Escape Apply ANSI standards and enclose the outer joins in escape notation { oj ... } that is parsed by the driver and replaced with DBMS-specific grammar.
ANSI Apply ANSI standards.
PB Maintain rules that applied to PowerBuilder 7.

Default

OJSyntax = ANSI for IN9 and SYC, OJSyntax = ANSI_ESCAPE for ADO.NET, ODBC, and OLE DB, OJSyntax = PB for O90 and O10.

Usage

All DataWindow Designer database interfaces provide support for ANSI SQL-92 outer join SQL syntax generation. DataWindow Designer supports both left and right outer joins in graphics mode and full outer and inner joins in syntax mode.

You must set the OJSyntax parameter to indicate the version of outer join SQL syntax you want DataWindow Designer to generate. For ADO.NET, ODBC, and OLE DB, the default is ANSI_Escape and can be reset to ANSI or PB (native). For IN9 and SYC, the default is ANSI and can be reset to PB. For O90 and O10, the default is PB, which means use Oracle native outer join syntax, and can be reset to ANSI.

OJSyntax is a dynamic parameter in all database drivers that support it. It can therefore be changed at any time during the life of a database connection with a statement such as:

SQLCA.DbParameter="OJSyntax='ANSI_ESCAPE' "

Define outer joins in the SQL painter for portability When you define an outer join SELECT statement graphically in the SQL painter, the DataWindow object stores the SQL in pseudocode. At runtime, the outer join syntax is generated based on the current OJSyntax parameter setting. This provides some degree of portability for DataWindow objects among multiple DMBSs.

When you define an outer join SELECT statement in syntax mode, the DataWindow object stores the SQL as syntax. This syntax is used without modification at runtime. The OJSyntax parameter setting does not affect the SQL.

Using native outer join syntax The option PB generates native outer join syntax. It is available for ODBC and OLE DB only if PBOuterJoin and PBOuterJoinOperator syntax entries are set in the appropriate SYNTAX section for your DBMS in the Sybase\DataWindow Designer 2.0\pbodb105.ini file.

For more information about outer joins, see the section on using ANSI outer joins in the DataWindow Designer User’s Guide.

OJSyntax does not apply to DIR For one database interface, DIR, the database connection always uses ANSI outer join SQL syntax.

Examples

Example 1

To set the value of OJSyntax:

Database profile Select the appropriate value from the Outer Join Syntax drop-down list on the Syntax tab in the Database Profile Setup dialog box.
Application Type the following in code:
```
SQLCA.DbParameter="OJSyntax='ANSI'"
```