Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!labrea!lindy!liemandt From: liemandt@lindy.Stanford.EDU (Joe Liemandt) Newsgroups: comp.sys.mac Subject: Re: 4th Dimension Message-ID: <2653@lindy.Stanford.EDU> Date: 9 Apr 89 08:24:40 GMT References: <1505@ccnysci.UUCP> Sender: liemandt@lindy.Stanford.EDU (Joe Liemandt) Reply-To: liemandt@lindy.Stanford.EDU (Joe Liemandt) Organization: Instruction and Research Information Services, Stanford Univ. Lines: 29 In article <1505@ccnysci.UUCP> alexis@ccnysci.UUCP (Alexis Rosen) writes: >In article rs5o+@andrew.cmu.edu >(Randall Knowles Smith) writes: >>Comments on 4th Dimension: >>The manual looks very good, and is quite authoritatively wrong or >>misleading in some parts. Not many, just enough to drive a beginner >>mad. Experts in Database programming probably wouldn't have any >>problems. Also, the program can be very slow at times; especially when >>running in a multi-user environment off a server. And this leads me into: > >That's not all. Often the manual is right and the program's wrong. Like >when it crashes. Which it does frequently, especially in multi-user. >Also, you're wrong. Even experts can go nuts trying to piece together >the crazily implemented input loop. This is wrong. 4D is a solid program. I have built over 20 multi-user apps in 4D. Everyday over 100 people use these apps and they do not crash. A 4D app is completely reliable. It is possible to cause 4D to crash if you call an illegal command that changes the current record pointer while entering a record. It is a bug that 4D crashes, but once you remove the illegal command, everything is fine. This is fixed in the new version. Joe Liemandt liemandt@jessica.stanford.edu