Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!aramis.rutgers.edu!paul.rutgers.edu!yes.rutgers.edu!emuleomo From: emuleomo@yes.rutgers.edu (Emuleomo) Newsgroups: comp.databases Subject: Re: foxpro compatibility??? Message-ID: Date: 11 Oct 89 11:49:59 GMT References: Organization: Rutgers Univ., New Brunswick, N.J. Lines: 39 In article , ms7u+@andrew.cmu.edu (Michael C. Sanders) writes: > I need some help ... > > We are working on upgrading some Dbase 3 code to increase speed and > performance. We are considering using either Foxbase, Clipper, Dbase 4, > or Foxpro. The problem is that the current system is quite large and > we do not want to have to rework the code (for compatibility's sake) if > we don't have to. > > So --- My main question is what compatibility problems will we run into > when using DBase 3 code on one of the other database programs. > > Thank You, > Foxbase+ 2.0 or 2.1 is *definitely* the way to go. It will run your dBASE code WITHOUT you having to rewrite a *SINGLE* line of code. It will also run it about 2-6 times faster!! As an added bonus, it gives you an identical dbase programming environment. *That's why they got sued by A-T*!! If you "compile" your application using Foxpcomp, it will run even faster.! Yes, before I forget, Fox uses its own proprietary index files but it will automatically reindex any dBASE index that your program needs to use *ON THE FLY*. Neat stuff! I can't recommend clipper, because it is not 100% compatible with dBASE3. Forget dBASE IV; at least for now. From what I hear, it is not stable yet! Foxpro is still vapourware. I havent seen it yet. Also the suggested retail ($795) is too expensive for me. You can get Foxbase+ version 2.1 for about $190 I beleive! Hope this helps. --Emuleomo O.O. (emuleomo@yes.rutgers.edu) -- ** Writing error-free code MUST be magic! Why else is it sooo difficult to do?