Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!hacgate!ashtate!dbase!cy
From: cy@dbase.a-t.com (Cy Shuster)
Newsgroups: comp.databases
Subject: Re: dbase IV "popup" while editing data with "read" command
Keywords: dbase, data entry
Message-ID: <1991May9.171906.15594@dbase.a-t.com>
Date: 9 May 91 17:19:06 GMT
References: <1991Apr17.110913.7460@bhpmrl.oz.au> <1991Apr22.170319.24538@dbase.A-T.COM> <1991May4.063752.10314@resmel.bhp.com.au>
Reply-To: cy@dbase.UUCP (Cy Shuster)
Organization: Ashton-Tate
Lines: 21

In article <1991May4.063752.10314@resmel.bhp.com.au> paulg@resmel.bhp.com.au (Paul Gallagher) writes:
>Niggles (not strictly problems) I have are :
>    (1) <Deleted - modi comm>
>
>    (2) Is BUILD/DBLINK meant for serious applications? (more
>        than just "Hello, world"). I've tried 386 machines
>        with 4Mb+ configured in every which way, but cannot
>        build & link even the most basic application
>        without getting an out-of-memory error.

Right you are. An interesting workaround came up during the beta testing
of dBASE IV/Macintosh: when our user's application wouldn't dBLINK with
600K free on the PC, I suggested he move the .DBOs to the Macintosh and
try it there (the Mac product is primarily RunTime, but we have a Toolkit
that includes dBLINK). Sure enough, with 2 meg of memory, it worked.
Final .DBO size was only 312K. And, it executed perfectly when copied
back to the PC.

--Cy--
cy@dbase.a-t.com