Thanks Daniel, you raise exactly the issues we have been discussing. We'd never thought about a .DBC'less application, but it makes sense from your comments. It is an interesting concept.


>Both have their good points and bad points. Personally I prefer to use SPT when possible because (1) you don't have to have a DBC, (2) you can send commands straight to SQL (either dynamically built statements or calls to stored procedures), and (3) they are often (but not always) faster. As far as I'm concerned, SPT offers the developer an incredible amount of flexibility, something I wouldn't want to give up.

Remote views, on the other hand, are useful if you have to present groups of records to the UI, such as in a grid. RV reaction time has been greatly enhanced, but you still are bringing data to the client every time you want to do any kind of operation. Also, they can be a PITA to work with when adding new records, because you are adding info on the client side - none of your DB-bound defaults will fire UNTIL you insert the record.