>Hi John:
>
>I stand with you on this one. RV's are defintely 'Old School'! Until you build a client server app that relies on SP's for data access, you'll never know what high performance is all about. VFP with its OOP data classes makes building a generic framework for working this way really easy. Also, IMO a side benefit of moving your data access code into stored procedures greatly simplifies application development
>
>I spent about 8 months developing a set of data classes for a client server app for the Navy IG. My goal was to do all data access in SP's (SQL Server) and absolutely minimize round trips to the server. Even keys where generated on the client! When all was said and done, it performed so well, that when it came time to demo the app I chose to do it through an ordinary 56K modem!
>
>Charlie

Charlie,

Were you using stored procedures to do updates, deletes and inserts as well? We've had quite a bit of discussion here over the best way to do things. Current literature claims that doing everything through stored procedures is faster. However, in my mind, the concept of three tier starts to get a little blury. Remote views are simple to create, but tend to be somewhat slow. As far as updating multiple tables, you can do it by wrapping everything in an event, but then transaction handling becomes really hairy. I would like the best of both worlds.