emjej@uokvax.UUCP (11/21/84)
I would be interested in any information about lists of bugs and common workarounds for dBASE II, the more comprehensive the better. Quite frankly, there have been so many things go wrong in an application that I have been working on that I cannot in good faith recommend dBASE II to anyone for any purpose whatsoever. Examples: dBASE II takes the system into oblivion if a procedure is lacking an ENDDO/ENDCASE (i.e. one matching a corresponding DO). Ditto if there is a syntax error while one has output to the screen turned off (as one must to get a report printed only on the printer). When one switches Master Indexes repeatedly, dBASE II appears to get confused, and may be responsible for trashing the disk allocation map. dBASE II responds to any and all OS calls that come back with an error return with the message "DISK IS FULL." James Jones
emjej@uokvax.UUCP (12/03/84)
/***** uokvax:net.micro / emjej / 2:14 am Nov 21, 1984 */ [dBASE II takes the system into the Twilight Zone] if there is a syntax error while one has output to the screen turned off (as one must to get a report printed only on the printer). /* ---------- */ Well--I find I must point out that this may not be exactly what happens. It *may* simply be that with output to the screen turned off, one's typed commands and its error messages aren't visible. While extremely obnoxious, that isn't *quite* so bad... "It's all right, Ma/I'm only in SET SCREEN OFF mode" James Jones