>I know that there is a SET REPORTBEHAVIOR, but is there also a Behavior setting to counter the changes from VFP 6.0 SQL type code to VFP 8 and 9? I don't want to have to re-write my code.

Keep in mind that there was a very good reason for the change in the SQL engine. This means that with Set engingebehavior 70 or 80 you may end up with wrong data! So unless you want to take risks, you really should change your select statements!! The ONLY reason for using Set enginebehavior to a lower value, is to avoid errors during developement, so that you can fix one select statement at a time.