>>Can anyone give me 3 good reasons for using SQL pass thru' for client server applications instead of using remote views?
>>
>>Regards
>>JohnH
>
>Well... considering that a View uses SPT... the only reason I can see is if you want to send a SQL statement that you can not store in a view...such as running a stored procedure.
>
>Well... if you create the view programatically then you can basically use ANY SQL that you want, even SQL that Fox would not understand but the backend would.
>
>You can even build the view 'on-the-fly'... but, as someone here said, you have to have a .DBC open.
>
>BOb

We have a schema that uses two paired connections to the SQL Server backend. One handling transaction volume and one handling SQL Pass Through. The result is very nimble response.

SPT provides a level of versatility that the view designer doesn't. Note, the weakness is in the designer, not SQL. (ex. A situation where you want to retrieve data into a view that may come from any one of several tables that are structurally identical.)

Regards,