Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!hacgate!ashtate!dbase!awd
From: awd@dbase.A-T.COM (Alastair Dallas)
Newsgroups: comp.databases
Subject: Re: Dbase IV compiler
Summary: I forgot RunTime
Keywords: Why no answer?
Message-ID: <436@dbase.A-T.COM>
Date: 16 Feb 90 05:46:33 GMT
References: <125695@infocenter.UUCP> <418@dbase.A-T.COM> <19363@grebyn.com>
Organization: Ashton Tate Development Center Glendale, Calif.
Lines: 22

In article <19363@grebyn.com>, rwilliam@grebyn.com (Roger Williams) writes:
> 
> Hmmmm... Where I work, we have a copy of dBASE IV Developers
> Edition.  This Developers Edition allows you to generate .dbo
> files, link them with DBLINK and run them on machines that do not
> have dBASE via the RunTime module that was included in the
> Developer's Edition.  I'm a bit suprised Alastair didn't mention
> this.

Well....  I try to avoid hype if possible.  RunTime is extremely useful
and worthwhile for developers, but to create the "RunTime" module, we
#define RUNTIME and recompile the source--the 'module' is very large
because it contains a large percentage of dBASE.  You get code security,
a single DBLINKed dbo file and turnkey operation, but you get almost none
of the efficiency people associate with a standalone executable.  

But you're right--I was reading into the original poster's request the
need for features I'm waiting for in our Professional Compiler; perhaps
RunTime is just what he needs.  Thanks for catching me!

/alastair/