Dustin,
As others have said, the work is done on the SQL Server box. Here's why.

Remote views are a user-friendly (sometimes) wrapper for SQL pass-thru. A query is built using the information stored in the DBC (SQL statement, parameters, etc.) and that is sent to the server for processing. The same thing can be done manually by:

Create a SQL Select statement

Create a connection to SQL Server using SQLConnect() or SQLStringConnect()

Get a result set using SQLExec() and the SQL statement

Make the result set read/write

Make your changes

Process the result set to determine which records have changed

Process the changed records to determine which fields have changed

Create a SQL Update statement using the new field values

Send the SQL statement to SQL Server using SQLExec()

You can create this and many developers have in the form a data management objects. Once they are created they are better because of the flexibility. You can determine how the updates are done; whether in the form of a passed Update statement or in the form of a stored procedure call. You don't have to rely on the VFP internals.

The debate that was mentioned was between two camps: those that already have the data management objects and those that have not spent the time to create them (even though they could). The Return on Investment (ROI) is not there for them because RVs do work.

>If I make a Connection in the VFP DBC, and then make a remote view using that Connection... I'm able to see Tables and Views made inside our SQL Server. So far so good.

>However, if I pick SQL tables, do joins, and then set a parametered filter... where does that work get done? Does that work get done on the client side, or inside the SQL server?
>
>What I see happening is one of 2 things. Either the remote view pushes the SQL code through (including the filter), and SQL does the work sending back only the 1 or so records - that'd be great.
>OR-- the remote view pulls the whole database info over, and then does the filtering locally (bad).
>
>Does anyone make views inside the SQL server? I'd like to... Easier to maintain and create I think but they don't allow Parameters. So does that mean I should just make them in the remote view section on VFP?
>
>Thanks,
>Dustin

Larry Miller
MCSD
LWMiller3@verizon.net

Accumulate learning by study, understand what you learn by questioning. -- Mingjiao