>1 - Why do they "suck"? what is it that is so bad?

>2 - without them - what is the best way to get the user an updatable subset of records to work with in your opinion?

Remote views are at best, an incomplete wrapper for SQL-Passthrough. The idea and concept around them in theory is nice. I equate remote views to the Design Time Controls in Visual Interdev, another layer that separates you from what you are attemting to work with, in this case data. By ceding control to Remote Views, you give up the level of control you really need. The only implementation of remote views that I have seen worked use a combination of the view itself and SPT for updates. To take this a step further, the best model I have seen and have worked with is one that consists of using stored procedures for all updates, inserts, and deletes, as well as list generation.

Remote Views are a VFP-Only implementation that does not play well in an N-Tier envronment.

Just my 2-cents here.



>PS (Local PA guy insider question) - you guys get any rain up there yseterday? not a drop down here (in Boothwyn just above Deleware border)

No rain whatsoever. It is getting pretty bad here...