Walter,

>Jim,
>
>>>I did ??? Well I've must have been drunk.. ;-) I'll review my post to see where I was uncarefull.
>
>>Without reviewing the prior, I remember a statement that RELEASE releasing only the memvar is OK by you. That is what I was referring to.
>
>Let me clarify myself. Yes when a variable is relaesed it may release it's object also. But what about other refering variables (or even more complex: properties of other objects). IHMO they should be set to .NULL. rather then being released also.
>

I see - my mistake. Fine with me.

>>>Yes, exactly, and what I also want is to do this implicitly by SQL (or xBase command) rather than explicitly.
>
>>>hmmm. This new topic is so new, i've got to rethink this whole issue before I can take a definite standpoint. Sure I like the idea, but have no idea how this should be implemented (syntax and new features, not C++ implementation).
>
>>To me too, actually (as far as HOW to get it done). That's also why a dialogue is so important on issues of this msgnitude, even if it turned out to be only the two of us < S >. We'll have to find some way to get one going.
>
>Yup, I agree...
>
>Jim, Why don't we call you demand for a new whishlist section, just the Thinktank section. This would impose not only new whished, but also other opinions about already accomplished features or about difficult problems ?
>

I've promised myself to never ask for that one (or a disguised one like it). If someone else asks they will have my full support.

Jim

>
>Jim N