>Yes that is for sure the downside of doing it this way. I have run across a few situations where I really needed a stored procedure (or needed to run one that someone else had written). In those cases I just tackled them as they came up.

Yupp, I am also advocating to use what is needed in those special situations.
For CRUD and basic table layout a generic approach is workable,
and the special SP or access methods need to be put in one place
so they can be found and ported if push comes to shove,
but not spend too much time of making them portable for first shot.