Is it wise to have a class branch out to other classes?

As in: if I have a class dedicated to sending data from a form to a database, is it wise to have that class call other classes for adds, updates, deletes?  Or is that just complicating things needlessly?

Stupid question, but I'm curious if anybody's had experience with this scenario.

I don't see a problem calling other classes from within your class. Let's say you had a class that does special math functions and your class needs to call these functions then it would be logical to declare the class and use it. The thing is should you create seperate classes for every aspect of manipulation to this database or maybe bottle them up into this one class? I would probably tend to put them into one class with various methods; add, update, etc. I guess it all depends on how much these aspects fall into the logical order of things.

My 2 cents.

Thanks,

The more I learn about programming, the more I see the benefits of specialization and branching.  To me, a really well written piece of code is a thing of beauty.

It's always compact.  

It's always easy to modify and expand upon.  

It's always easy to "make go away" when you don't need it any more, and there are minimal if any repurcusions to other segments of code based on its absense.

Not that my code is always like this, of course, but when it is, I know I'm doing something right.

Well said.