home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!madrone.CS.Berkeley.EDU!rwahbe
- From: rwahbe@madrone.CS.Berkeley.EDU (Robert Wahbe)
- Newsgroups: comp.sys.mac.databases
- Subject: 4D v3.0 is Buggy
- Date: 10 Jan 1993 00:59:45 GMT
- Organization: UC Berkeley, University of California Berkeley
- Lines: 27
- Distribution: world
- Message-ID: <1inse1$no1@agate.berkeley.edu>
- NNTP-Posting-Host: madrone.cs.berkeley.edu
-
- I bought 4D v3.0 about 3-4 weeks ago and have been developing
- a fairly large application with it. Had I to do it over again,
- I doubt I would get 4D. I chose 4D because it is a well reviewed product
- and provided most of the user-interface hooks needed to build
- a user-friendly program. It requires substantially less
- user-interface programming than FoxPro.
- However, in these last weeks I have reported probably 10 reproducible
- bugs to 4D technical support.
- In addition, I have had many, many, system crashes that I cannot
- reproduce. Other bugs are easy to reporduce on my databases but
- 4D technical support can't seem to do it. An example is
- that on some layouts my rulers are incorrect. If you take two
- screens and line them up they disagree about where the 4 inch,5 inch, etc
- mark is.
-
- Today was probably the last straw. I spent an hour or so trying
- to figure out why, in certain contexts, the incorrect record
- was getting deleted. Well, it seems like a bug in "DELETE RECORD".
- I print out the current record, using "Record number",
- all along the way, including right before the call to "DELETE RECORD".
- Everything is fine until I look at what record has been deleted; not
- the current record!
-
- Anybody else have similar experiences with 4D?
-
- -Robert
-
-