RonKyle (8/21/2013)
As a VB Programmer, I developed a lot of processes using disconnected recordsets. I used stored procedures to retrieve the initial sets. However, the additions and changes made by the recordset object required direct access to the tables. For that reason alone, I couldn't have used views. I've seen this technique recommended before, but personally have found very little use for views in an OLTP environment. I've used them to some extent in an OLAP environment to allow me to pull a subset or higher level from a dimension table (e.g. create a quarter hour view from a dimension table that has all the minutes, a month view from a date dimension that has days or a sub list of inspectors from technicians). In one of the Kimball books I read recently views were recommended for all the tables so that the auditing information that was of no use to the end users could be shielded. This is also intriguing, but you can't set the referetial integrity among the views in the same manner as tables.
I too got a lot of mileage out of recordsets. One thing I will say is that while the default behavior of the recordsets was to go for direct access to the tables, it's actually very straightforward to switch them over to using nothing but stored procedures. Sure it adds a few minutes to the dev process - but I thought the extra work was worth every penny. The extra abstraction saved my bacon a few times, and allowed us to make changes on the DB side (such as - intercepting and validating certain changes) without redeploying the program.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?