oj syntax for outer join

[Former Member]

Is there a way to make Crystal Reports XI not generate the {oj ..... syntax for outer joins?

In Crystal Reports 8, you could do a registry change to keep CR from using oj, but that doesn't seem to work on CR XI (or I don't know where to make the registry change)

[kyle_mcadam · Accepted solution]

Outer Join Escape Sequence builds the syntax for ODBC drivers using the outer join syntax in its SQL syntax.

Use Regedit on the problem client machine add following keys:

STEP 1........For Crystal Reports 9: HKEY_CURRENT_USER\Software\Crystal Decisions\9.0\Crystal Reports\Database\QueryBuilder\OuterJoinEscSeq

<<<OR>>>

...................For Crystal Reports 10:HKEY_CURRENT_USER\Software\Crystal Decisions\10.0\Crystal Reports\Database\QueryBuilder\OuterJoinEscSeq

STEP 2........"MSOuterJoinEscSeq"= "insert your ODBC driver name here": List of the drivers that support Microsoft ODBC {oj ..} join escape sequence.

"NoOuterJoinEscSeq"= "insert your ODBC driver name here": List of the drivers that do not support any join escape sequence.

For example...

MSOuterJoinEscSeq = "UVODBC"

[Former Member · Accepted solution]

You have listed solutions for CR 9/10, but what about CR XI (CR 11)?

Edited by: Donald johnson on Oct 13, 2008 6:56 PM

[kyle_mcadam · Accepted solution]

\Business Objects\Suite 11.0\

would replace

\Crystal Decisions\10.0\

in the reg path.

Everything else would be the same*

*create the keys if they do not already exist

[Former Member · Accepted solution]

Key: HKEY_CURRENT_USER\Software\Business Objects\Suite 11.0\Crystal Reports\Database\QueryBuilder\OuterJoinEscSeq

Set the following String value (or create it)

NoOuterJoinEscSeq = MYODBC3, libmyodbc3

both MYODBC3 and libmyodbc3 must be in the value to work even though in the driver list only myodbc3.dll is shown.

[Former Member]

Any idea how the registry is configured for Crystal Reports 2008 to exclude the {oj please ?