Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uwvax!umn-d-ub!umn-cs!nic.MR.NET!hal!ncoast!telotech!bsa
From: bsa@telotech.UUCP (Brandon S. Allbery)
Newsgroups: comp.databases
Subject: Re: Why Does FoxBase Act Like a Virus?
Message-ID: <1989Oct27.170621.27641@telotech.uucp>
Date: 27 Oct 89 17:06:21 GMT
References: <1989Oct24.153944.29979@agate.berkeley.edu>
Sender: bsa@telotech.uucp (Brandon S. Allbery)
Reply-To: bsa@telotech.UUCP (Brandon S. Allbery)
Organization: _
	      telotech, inc. - Beachwood, OH
Lines: 28
In-reply-to: steve@violet.berkeley.edu (Steve Goldfield)

In article <1989Oct24.153944.29979@agate.berkeley.edu>, steve@violet (Steve Goldfield) writes:
+---------------
| mention in the subject above. FoxBase takes over both
| data and program files and changes their type so that
+---------------

Assuming you're talking about FoxBase+/Mac, what FoxBase does is no different
from what any word processor does.

+---------------
| I declared a variable public in one program and set it to a
| value, but in the next program I ran the variable was declared
| not to have a value. I'm not strongly motivated to use FoxBase
| if the programming features I'm used to using don't work.
+---------------

As far as I've been able to tell, the MS-Doesn't versions of both FoxBase and
dBase III+ require that you declare a variable PUBLIC in *all* procedures that
want to use the public copy.  Probably the Mac versions of both do the same.
I don't know anything about McMax, so I can't comment on its handling of
PUBLIC variables.

++Brandon
-- 
-=> Brandon S. Allbery @ telotech, inc.   (I do not speak for telotech.) <=-
Any comp.sources.misc postings sent to this address will be DISCARDED -- use
allbery@uunet.UU.NET instead. My boss doesn't pay me to moderate newsgroups.
** allbery@NCoast.ORG ** uunet!hal.cwru.edu!ncoast!{allbery,telotech!bsa} **