> > No, it can be an array. But unless it really needs to be part of
 > > every class instance, why not simply make it 'static'?

 > yeS, mAkiNg it StAtiC will Solve the pRoblem, but the
 > trouble is I have to create several separate classes.
 > What should I do?

If the classes are related (as I would guess that they are if they are to
access some data in a particular way), then if derived classes need access
to the static data, then make it 'protected' or 'public'. If they aren't
related (why aren't they? Do they describe the same or similar
"things"?), then just make it a global variable.

  David

---