HS> I fail to see the big hype about OOP & OOD.
 HS> Please explain where it can be used and how this will make it
PP>better.
 HS> I am thouroughly familiar with OOP & OOD so there's no need for a
 HS> definition.
PP>For example, in this OO database I made (a casket inventory management
PP>program, where a casket is made of a case, handles/ornaments, an
PP>interior, plus some options (lighting, sealing, etc...)), there's a
PP>TItem class and a TModel class, which is a descendant of TItem. I have
PP>this single database of TItem, that (through polymorphism) can contain
PP>both TItem objects and TModel objects. So you can sell both a complete
PP>casket (a TModel object) or a single replacement handle for a broken one
PP>(a TItem object). In *both* cases, those use the same code.
PP>This is a simple example, but for me, the biggest time saver is the
PP>sharing of code for multiple cases in a single program, next comes code
PP>reuse between many programs (like my filter classes, to encrypt/decrypt,
PP>compress/decompress, all on the fly, through a stream.
I've been reading some books on OOP lately and I have also found uses for it. 
Thanks for replying..
PP>Pierre
... Hi, my name is Annie Key. Please don't hit me!
--- Ezycom V1.48g0 01fd016b
---------------