NH>> void  ClassA::DoitA()
NH>> {
NH>>    ClassB cb(this);
NH>> }

JB> yeah, the scope  above is contained between { and }

And that's where all the action takes place.  I didn't include it 
because creating and using the linked list has been done and working for 
some time, I just thought it would be nice to move that portion of code 
into its own class.

JB> If you don't want to do it then leave that constructor out.

Rather than just leave it out (in this case, the default constructor) I 
think that I'll have an assert() there so there will never be the chance 
of even trying to use it.

NH> Can you think of another, possibly better way to do this?

JB> depends how good your database stuff is...
JB> it might just need a little wrapper to behave like a linked list.

I'm using a relational database handler via ODBC.  That gives me very 
flexible database handling if I make the SQL calls correctly.  However I 
don't want to be doing any database manipulation in classes that 
obviously deal with non-database stuff.  Or IS it non-database stuff?  
Whatever... I'm just trying to compartmentalize the code to a greater 
degree.

Were you thinking of the "little wrapper" in a different way?

þ CMPQwk 1.42 999

--- Maximus/2 3.01