Since you already have a bunch of refactoring to do don't forget to convert the entire SQL.  What I mean by this is

Starting SQL:

SELECT...

FROM RED, BLUE, GREEN

WHERE RED.ID *= BLUE.ID

AND BLUE.ID = GREEN.ID

Correctly rewritten:

SELECT...

FROM RED

LEFT JOIN BLUE ON RED.ID = BLUE.ID

JOIN GREEN ON BLUE.ID = GREEN.ID

Incorrectly rewritten:

SELECT...

FROM RED, GREEN

LEFT JOIN BLUE ON RED.ID = BLUE.ID

WHERE GREEN.ID = BLUE.ID

Apart from Chris' great advice, here are 2 tips:

1. just in case: search not only for *= but also for =*

2. if you use Sql Sever management studio, you can create a new query using the query designer ( CTRL+SHIFT+Q). You can then paste your "old" SQL and your old sql will automatically be converted to modern SQL. It might save you some headaches. (I'm using the latest SSMS from the free sqlserver developer edition).

regards

Hi Will;

  If the DWO objects were built where the SQL was saved in Graphics mode, then the Transaction Object's DBParm setting controls the join syntax automatically, as follows:

SQLCA.DBParm = "OJSyntax='PB'"             // VS

SQLCA.DBParm = "OJSyntax='ANSI_Escape'"    // VS

SQLCA.DBParm = "OJSyntax='ANSI'" 

  If you saved the SQL from the DW Painter "As Syntax" - then you will need to update every DWO's SQL manually. Of course, in-line SQL is going to be a manual update anyway. That is why I always recommend...

1. Never use in-line SQL. Use a DWO instead.
2. Always build DWO's & save then in SQL Graphics mode.

HTH

Regards ... Chris