Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!rpi!uupsi!njin!princeton!njsmu!mccc!shevett
From: shevett@mccc.uucp (Dave Shevett)
Newsgroups: comp.databases
Subject: FoxPro questions
Message-ID: <1990Sep28.184053.20731@mccc.uucp>
Date: 28 Sep 90 18:40:53 GMT
Reply-To: shevett@mccc.edu (Dave Shevett)
Organization: The College On The Other Side of U. S. Route 1
Lines: 24

My company is in the process of converting 100,000+ lines of code over to
FoxPro from FoxBase 2.1.  We're a little cautious about the major
changeover, and are wondering about a few things:

1 - Has anyone had any real problems/bugs with FoxPro v1.02?  That's the
version we're running, and haven't had anything major crap out, but we just
want to be on the lookout for any problems.

2 - FoxPro Runtime v1.02 (and others) have an annoying 'enhancement' - on
older versions of FoxBase, you could use the message(1) function to return
the line of program code that caused an error.  Our error trapping routine
used to be able to show us the exact text of an error.  Apparently that
function has been nuked in FoxPro, unless the .PRG file is available in the
running directory.  This makes supporting our products very difficult, as
we would prefer not to distribute the source code to our clients. Has 
anyone either found a way around this or heard if Fox is going to put 
it back in?


/--------------------+                        +----------------------\
|    Dave Shevett    | "The shortest distance |   Labyrinth II BBS   |
|  Lawrenceville, NJ | between two puns is a  |    (609) 584-8774    |
|  shevett@mccc.UUCP | straight line..."      | 12/24/19200 PEP 24hrs|
\--------------------+        - Doc Webster   +----------------------/