>Schema changes are not uncommon during development. Often, a field will move from one table to another. Being a good developer has little or nothing to do with that. Not getting bogged down with a tool that cannot handle those changes, that is a mark of a good developer.
>
I know, that case is not uncommon but it also is supposed to happen very few times (since you already designed your app's database) but when One must rename or delete a field just remove it from the fields list, make the change on your table, and then change your fields list accordingly, it's just one little step more.


>In "theory" the database design is supposed to be frozen. In "reality", that is rarely the case.
>
I agree with you.


>As for how you split the use between RV's and SPT, if you use RV's for updating data, why don't you use RV's for queries? I could see why one would use a RV for queries and SPT for updates, since SPT gives you access to SP's.
I use RV because it aliviates the problem of setting every field property by code besides the view's own properties. They are many, many. And I can use the same view for many forms and they are easily available at my project. OTOH I use SPT because it is just necesary to write the SQL SELECT statement, I don't have to worry which fields are updatable or not.