Path: utzoo!utgpu!watmath!xenitec!timk From: timk@xenitec.on.ca (Tim Kuehn) Newsgroups: comp.databases Subject: Re: Why Does FoxBase Act Like a Virus? (WRONG!!!) Message-ID: <1989Oct26.010852.11879@xenitec.on.ca> Date: 26 Oct 89 01:08:52 GMT Reply-To: timk@xenitec.UUCP (Tim Kuehn) Organization: TDK Consulting Lines: 49 steve@violet.berkeley.edu (Steve Goldfield) writes: First off I takes strong exception to relating Foxbase/+ to ANYTHING other than the high-quality dbaseIII+ compatable rdms it is. (And especially to viri of any sort!!) Another post has explained why things happen in the Mac version of f-base. I'll touch the following problem: >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. > >Steve Goldfield Did you check the procedure your were running in to make sure that it didn't have a PRIVATE statement with the same variable name. if you do something like this: public varxyz . . .<.....code here . . procedure try_me private varxyz q = varxyz When you run try_me you're going to get an error since the public variable is not 'visible' to the local procedure, which has a variable declared private (ie local) with the same name. In closing, before you condem a product (particularly one that's had so many glowing reports from almost unbiased sources :-) ) make SURE of your claims!! (You'll get less egg-foo-young on your face that way! :-) ) +-----------------------------------------------------------------------------+ |Timothy D. Kuehn timk@xenitec.on.ca | |TDK Consulting Services !watmath!xenitec!timk | |871 Victoria St. North, Suite 217A | |Kitchener, Ontario, Canada N2B 3S4 (519)-741-3623 | |DOS/Xenix - SW/HW. uC, uP, DBMS. Satisfaction Guaranteed| +-----------------------------------------------------------------------------+