Vin,

>First of all, I was not offering any advice without reason. I assume that your "you" is meant in the sense of "one" and not geared toward me, or perhaps that you have mistaken me for someone else.
>
>Second, that thread was full of folks offering reasons. You have offered some good testimony here (in an earlier post) as to the pros and cons. I've got to tell you though, that to me, the tighter control that SPT provides is increasingly desirable as system size and complexity increases. I suppose that my wise-ass response to your question was due to my sense that this question was a) self-evident, and b) supported by previous posts.

The idea of something being "self-evident" or "supported by previous posts" is very subjective. I often have questions about things that other people find obvious because they have dealt with it. But I need to ask questions to learn.

>It was as if I had been following a thread where several post-ers discussed the reasons for centralizing code in classes rather than in the Click() events of command buttons, and then someone pointed out in a bulleted list that "enterprise system will benefit from moving code into separate objects" only to have someone respond "Why?" Come on, what's next? Why use a primary key? Why use a table? Why comment your code?

I don't think any question is a bad one when it is asked constructively and with an open mind. Sure, some of Erik's "whys" were a bit stubborn, but never degrading to other posters or dismissive of salient facts. As for "why use a primary key" or "why use a table", heck, I have seen plenty of discussions about such things, and I think they are good! Some people have very good reasons for not using such things, or putting twists on the old stand-bys. I don't think there's anything wrong with discussing these "self-evident" issues.

JoeK