Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site uokvax.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!uokvax!emjej
From: emjej@uokvax.UUCP
Newsgroups: net.micro
Subject: dBASE II bug list wanted
Message-ID: <3400051@uokvax.UUCP>
Date: Wed, 21-Nov-84 03:14:00 EST
Article-I.D.: uokvax.3400051
Posted: Wed Nov 21 03:14:00 1984
Date-Received: Sun, 25-Nov-84 03:35:42 EST
Lines: 19
Nf-ID: #N:uokvax:3400051:000:888
Nf-From: uokvax!emjej    Nov 21 02:14:00 1984

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