>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?
>

If you use the MS ODBC drivers for Oracle, those drivers are [should be] responsible for converting MS SQL syntax to Oracle SQL syntax.

The problem with the VFP view designer is when you have 3 or more tables to join. The designer will nest the joins which can cause a problem when you try to open the view or re-edit the view in the designer again. Most of us will use the designer to create the initial SQL command, view the SQL code while in the designer, block the code to then copy and paste the code into a PRG file. Setting the properties [updatable, etc.] of the view is also programmatic at this point also.

Don't know about any relative in Goldthwaite. Most of mine are in the bustling northeast Texas towns of Atlanta, Queen City and Texarkana.