Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!cernvax!ethz!forty2!eichi
From: eichi@forty2.UUCP (Stefan Eichenberger)
Newsgroups: comp.databases
Subject: Re: DBASE IV BUG(S)
Message-ID: <702@forty2.UUCP>
Date: 2 May 89 20:13:35 GMT
References: <2178@muvms1.bitnet> <701@forty2.UUCP>
Reply-To: eichi@forty2.UUCP (Stefan Eichenberger)
Organization: Exp. Physics University Zuerich
Lines: 29

One more bug (?), I forgot in my previous posting: From Clipper, I'm used
to control screen colors by something like

   ColorSet1 = 'GR+/G....'
   ColorSet2 = '.........'
   Set Color to &ColorSet1
   ...
   Set Color to &ColorSet2

This is perfectly leagal in Clipper and works in dBase IV procedures too,
although the manual tells you nothing about it. If you believe the manual,
Set Color to does not expect a character expression. OK., it works in
procedures, but where is the bug?

Try it in functions, and you learn, that macro substitution is not supported
in functions... The manual contains a list of commands that are illegal in
functions, macros are, of course, not listed there. Is it a bug, or is the
information simply too good hidden in the manual?

I'd also have some questions on how to do some things from within programs,
which are easy in Clipper, but can't be done in dBase IV at all (i.g., 
terminating READs by function keys and react on them accordingly), but I
think it's too much efford typing them concerning a package, I'll hopefully
never use again.
-- 
----------------------------------------------------------------------------
UUCP:      ...mcvax!cernvax!forty2!eichi         Stefan Eichenberger
BITNET:    K807817@CZHRZU1A
----------------------------------------------------------------------------