Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ns-mx!umaxc.weeg.uiowa.edu
From: lbrintle@umaxc.weeg.uiowa.edu (Lee Brintle,Advantage,337-5200,3374010)
Newsgroups: comp.databases
Subject: Re: FoxPro questions
Message-ID: <2001@ns-mx.uiowa.edu>
Date: 30 Jul 90 21:33:21 GMT
References: <5433@uwm.edu>
Sender: news@ns-mx.uiowa.edu
Lines: 25

From article <5433@uwm.edu>, by gibsonlp@csd4.csd.uwm.edu (Dean A Herman):
> Questions, questions, questions. In my eternal wisdom, I turn to the net.

> 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.

The development version of FoxPro does not compile down to ".EXE" files;
in fact, no current FoxPro product (as far as I know) does compile to 
.EXE.  They compile down to .FXP P-Code, which is then interpreted at 
run-time.  Full FoxPro takes up around a Meg, the run-time (which only 
runs .FXP's, but does not create them) takes around 850K.

Fox does, however, say that they will be coming out with an .EXE compiler
sometime early next year.  


lbrintle@umaxc.weeg.uiowa.edu
Lee Brintle