Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!wuarchive!udel!princeton!njsmu!mccc!shevett
From: shevett@mccc.edu (Dave Shevett)
Newsgroups: comp.databases
Subject: FoxPro questions
Message-ID: <1991Apr29.141335.19497@mccc.edu>
Date: 29 Apr 91 14:13:35 GMT
Organization: The College On The Other Side of U. S. Route 1
Lines: 45

We have some 'oddities' cropping up in FoxPro, and we're wondering if some
folks should shed some light on them:

1 - We use 'foxswap' to shell out to applications we're calling from the
programs.  (A graphics routine, and a communications program).  THe problem
is, repeated usage of this functions tends to accumulate lost clusters on
the drive.  Has anyone else seen this phenomenon?  We're having a helluva
time finding what's cauusing it.

2 - We have a menu that has a pick that may or may not be available, 
depending on the existence of a file.  The applicable code follows:


oblslash = iif(file(filename),'','\')

define menu reps
define pad obl  of reps prompt oblslash+'3  Out-Bound Bills of Lading (003)'  at 7,30
define pad exit of reps prompt '9  Return to Main Menu           ' at 10,30
                                                                        
on sele pad obl  of reps do rpick with pad()
on sele pad exit of reps do rpick with pad()

The problem is the first time we ACTI the menu, it comes up with option
3 disabled, like we want it to.  Then we hide it, and deac it.  The *next*
time we make the pick for this menu, option 3 is still not available, but
is not greyed out on the screen.  This is more annoying than a problem, but
we're curious what's causing it.  Any suggestions?

3 - Our most critical problem is with memory.  We want to upgrade all our
customers to FoxPro, but it's memory appetite is appalling. Since we use
Carbon Copy to support our customers, and it munches up 60k when loaded,
we're usually left with right around 500k of memory.  I don't want to argue
with QEMM on every steenkin' machine in the world to free up memory
(although that does work fine here).  Any suggestions on either getting
FoxPro to use up less memory, or shrinking Carbon Copy or freeing up
general RAM?

Thanx for all (if any) responses!

 ,___,    .--------------------------------------------------------------.
 \o.o/   | Dave Shevett     | Unix-PC BOF | The shortest distance between |
( \_/ )  | Lawrenceville,NJ |  TCF  '91   | two puns is a Straight Line   |
 |_|_|   | shevett@mccc.EDU | Apr 20-21st |                -- Doc Webster |
          '--------------------------------------------------------------'