>The logic that actually PERFORMS the Updates, Inserts, Deletes, and Queries should be manifested as stored procs.. The calls to these items, either as SPT or via ADO can be on the middle tier...

You say "should be manifested". Why? I'm not busting balls here, I just want to learn.

>If the calls are in the middle tier components that are hosted by MTS, where is the problem? Please define this position in more detail...

Here, I'm am refering to n-phase commit code for a transaction envoked in an SP.

>Often, the developer can function as the DBA. This is more of an argument in semantics...

Agreed.

>While this may be your opinion, the basis with which you make your conclusions are general at best.

I'm learning. Guess I shouldn't make a conclusion until I have fully experienced the alternatives.

>The fact is, SP's solve more problems than they create. In reality, SP's don't create problems. Rather, they are just different.

The other case is not using them in situations where there may be better alternatives. Therefore, they neither solve or create problems. I'm not saying I know the whats, wheres, and whens of these situations - I'll learn more about this with more experience and our conversation will be more robust *bg*.

>It is a matter of LEARNING how to use SP's...

The most important thing you have said.