Reply-To: erik.wachtmeester@bighole.iaf.nl
Raymond Pesek wrote in a message to Erik Wachtmeester:
EW ->The type(nPrivVar) check works OK if I declare a dummy public
   ->nPrivVar (with value NIL), that will be overruled when a
 RP> I always use ValType(), as there are some problems with Type(), and I
I know, but as I said, I tried them both. I prefer valtype() too, although I
don't know of any problems with type() (apart from the fact that it's not 
usable
on UDFs).
 RP> don't know of any other way around that problem. I've tried to 
 RP> handle it, also, and just decided it wasn't a good practice to have
 RP> uninitialized variables. I did what you did.
I agree, but in this case I had to cover uninitialized vars, because I needed
it in a couple of library functions that are used in 5 major applications and
about 20+ smaller interface application (linking a PABX, POS, etc. to one or
more of the major applications, etc.). I can't ask the office to update all
modules in about 80 hotels just because I needed this functionality in 3
modules...
But anyway, I guess you read my memvarblock-solution by now?
I love the way Nantucket/CA opened up the Clipper internals through 
codeblocks!
:-)
Regards,
Erik 
--- ifmail v.2.12-tx8.6
---------------