In addition to Jeff's note we can use SQL Pass-Through technology in VFP that allows to organize updatable cursor in VFP without any remote view. More, such cursor might be based on the data returned from SP! Just define which tables to update from which fields and thats all. As you see, SP is good thing only when used properly in the application.

>>With a RV, I need to modify the view to reflect the new order. I then need to distribute the RV. There are at least two steps. And if there is a costly aspect to the development game, it lies in software distribution.
>>
>>With a stored procuedure, I need to modify the procedure. There is nothing to distribute manually. I can make use of replication to automate the process of distibuting the change for me.
>>
>
>John,
>
>I agree that stored procedures are a beautiful thing, especially in terms of performance, data integrity etc. and are a very powerful tool for a database developer.
>
>I just thought I'd point out a scenario where using RV's would mean less modification if the user wishes to change the sort/filter/fieldlist criteria in the app than a stored procedure (which would require the modification of the actual SP on the back-end).
>
>You could have a dynamically constructed RV (it is, after all, an SQL Statement) that builds the SQL statement and then makes the call to CREATE SQL VIEW REMOTE blah blah AS based on the criteria that the user enters. This method does not require any changing of code on the client and I found it quite effective for the query tool-generated picklists in an app I previously worked on.
>
>Regards,
>
>-JT

Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.com
ICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs

It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.