>We are about to undertake a massive rewrite of one of our apps and have made the decision to move to SQL Server for data storage instead of VFP tables.
>
>We are undecided on using remote views or SQL passthrough for accessing the data. I realize that using SQL passthrough I will have the ability to fire stored procedures and can't do this with remote views. Other than that is there a performance benefit from either.
>
>One problem we may run into is that a user may leave the system running on their workstation for an extended period of time. Will either method allow that users system to see changes made by others on the network without requerying the db with either of these methods?
>
>One last thing... In real world example what is the benefit of using stored procedures in a desktop application?
>
>Thanks...
Tommy,

I'm not going to try to convince you either way. Rather, I'd suggest that you read Robert Green's "Integrating SQL Server with Visual FoxPro" and "Building Three-Tier Client/Server Applications with Visual FoxPro". Both articles are in the MSDN Library and can be accessed at the VFP web site. Simply do a search on Robert's name.

I would caution you, however, to re-engineer the application completely. FoxPro is a great ISAM data storage tool. OTOH, SQL Server functions best as a set based data storage tool. Don't succumb to the temptation of trying to use the same techniques you used with VFP tables on SQL Server.

As for stored procedures in a desktop environment, they be used to help segregate the UI from the business logic. This can greatly ease deployment issues because when a change is made only the server side has to be updated.