Doesn't the level of conversion of the VFP syntax to Oracle SQL syntax depend somewhat on the ODBC driver being used? I've had to create remote views in VFP using the Oracle outer join syntax because my ODBC driver couldn't convert the VFP syntax into Oracle. I had to create the outer join from the command window. The Database Designer couldn't do the job. The join worked OK until I made the mistake of trying to open it in the Database Designer. The Designer dumped it and I had to recreate the join from code again. I believe that I was using a Microsoft ODBC driver. The first ODBC driver I ever used between Oracle and VFP was a problem. It wouldn't conserve the long file names from Oracle. It doesn't seem that not all ODBC drivers handle syntactical differences as well as it seems they should. What ODBC driver do you use between Oracle and VFP?

You're not kin to any McCaslands from down around Goldthwaite, TX, are you?

Gregg

>It is the ODBC drivers that actually convert from VFP syntax to Oracle SQL syntax.
>
>Personally, I like the VFP version better because it is easier to understand, IMHO. I always got the plus-signs screwed up in Oracle. You can use VFP syntax in SQL Pass-thru because [as long as] the ODBC drivers are still being used as an intermediate step to Oracle.
>
>>Oracle has its own extension of SQL called SQL/PL (PL = procedure
>>language). As far as I know, you can only use standard SQL when
>>utilizing VFP and Oracle via SQL Passthru.
>>
>>You will find that Oralce SQL is not very compliant to the SQL-92
>>standard. This kind of surprised me. To see what I mean, compare
>>and contrast a LEFT OUTER JOIN between SQL Server and Fox versus
>>Oracle's (+) command.