Please don't top post!

Perhaps you should give us some examples of what you are trying to do
and we might be able to make suggestions.

It should be obvious when to make classes. A class represents some
thing, an Object. For example, an Apple, Orange or a Book. A class can
also represent something less physical such as a database. You don't
make a class to put a method in it.

Lionel.

You create classes based on the types of objects in the real world.

And you add methods to those based on something that makes sense
in the real world.

If two different ways both make sense in the real world, then
you should not worry about it in the code.

Maybe you should try and post a specific example that
is puzzling you, then we can try and explain what the above
means in that case.

Arne

Before beginning to code, try to get a feel of what the paradigm of
object oriented programming is. Once you are familiar with the
methodolody of encapsulation, data abstraction, inheritance and
polymorphism, you will be able to look at problems a lot differently
than the traditional procedural way. If you skip this step, even though
you'd be programming in an object oriented language, the code will
still end up being procedural.

-cheers,
Manish