That's one way you can do this and in general yes, this is good design
because it abstracts all of the relevant and possibly reusable pieces such
as addresses in its own class. By having a separate class for example you
can implement the validation code for hte Address object and then reuse it
in multiple places.
However, this is not necessary and deciding what becomes a new class or what
is simply a native member of the parent class is a matter of design and
depends on the functionality implemented. Hierarchical class implementations
are very common and promote a logical layout of classes that map real life
dependencies in many situations.
+++ Rick ---
West Wind Technologies
Making waves on the Web
"Jake s" <reachJakehotmail.com> wrote in message
news:037101c34a60$68fb95a0$a601280aphx.gbl...> Hi all,
> I am trying to determin the best way to implement a class.
> When I declare a class for example a person class I will
> develop it as follow:
> class personDetails()
> public firstname as string
> end Class
> Class person()
> public function getDetails() as personDetails
> dim objPersonDetails as PersonDetails
> objPersonDetails.firstname = "Tom"
> return objPersonDetails
> end function
> end class
> Is this the best way to implement? Any feedback would be
> Cheers Jake