Path: utzoo!attcan!uunet!lll-winken!uwm.edu!csd4.csd.uwm.edu!gibsonlp From: gibsonlp@csd4.csd.uwm.edu (Dean A Herman) Newsgroups: comp.databases Subject: FoxPro questions Message-ID: <5433@uwm.edu> Date: 30 Jul 90 17:47:18 GMT Sender: news@uwm.edu Reply-To: gibsonlp@csd4.csd.uwm.edu (Dean A Herman) Organization: University of Wisconsin-Milwaukee Lines: 35 Questions, questions, questions. In my eternal wisdom, I turn to the net. After two years of bashing my head against a brick wall "programming" in dBase III+, I'm ready for a change. Actually, I have no choice, a project I'm working on has grown to the point where dBase III+ can't handle any more. So, I've looked around for a better DBMS, mainly looking for speed and a better interface. The demo version of FoxPro 1.02 I've been playing with is, I think, the answer to all my problems. I need more than 15 index/ database/program files, the windows look great, and the mouse support has me walking pinching myself, since the users of this particular application all all upper-level management with little love for or knowledge of computers. I'm most interested in making .EXE files. The thought of having 2+ megs of hard-disk storage used up by dBase III+ or IV on every machine makes me shiver, it'd never do. Although I've read through all the nice glossy ads Fox sent me, and I've browsed the computer publications, I STILL can't tell if I can make .EXE's with FoxPro 1.02 alone, or if I have to go deeper and buy the "FoxPro Unlimited Runtime" at the same time. I am not interested in telling the client that they will need to purchase x versions of a NEW package, that'd never fly. But, if I can just make small .EXE's, they'll build statues in my honor. Also, anyone working with FoxPro...are there any significant drawbacks? It simply CAN'T be a step backwards from dBase III+. I'm working with about 30 databases, 7 of which are heavily used. Importing/exporting is a time consuming headache now, since the databases being moved have up to 150 records in them. I also have a good deal of reports which look into five or six databases. They aren't slow, but I'm wondering how efficient FoxPro is with large databases, and jumping back and forth between numerous databases. As you may guess, any information would be GREATLY appreciated. - Dean Herman gibsonlp@csd4.csd.uwm.edu