Evaluating opinions - FilePro Error Messages

[Nancy Palmquist]

"Jay R. Ashworth" wrote:

snip...
> 
> > I can never support that. The issue with using GETNEXT or GETPREV in
> > any loop that changes the key or deletes records is a well known NO NO
> > in the filePro programming world. NEVER EVER use GETNEXT or GETPREV in
> > these situations.
> 
> Why is it well known, Nancy?  Does the manual say not to do it?

Why should it have to?  The manual provides a reference.  That means it
tells you what 
each command will do and what it won't do.  It does not tell you what
order you need to 
do them in.  That is the part they pay you to do.  Just like the
dictionary defines the 
words you may use when writing, but it does not tell you what order to
use them in and 
how to make something meaningful out of the words.  That is what the
writer must do.

> 
> But since, as I noted, it would take about 3 lines in the sources to
> fix it, condoning it doesn't seem the best solution either.

So you suggest that they refuse to allow you to change data that you
have posted into a key
field because sometime in the future you may want to do a getnext on
that index.  Or should we
not allow you do do the getnext from that point.  Maybe you have
intended it to move your position and
want to continue forward from there.  I do not want my tools to divine
my purpose.  I just want them
to behave consistently, that is enough.  

> 
> And that happens.  But, clearly, you can see what I mean when I'm not
> happy with error messages that *appear* to know what's wrong.
> 
> Much less saying it's a syntax error, when it's not.

But it actually is a syntax error.  I was using a declared variable
incorrectly.  By using
the same word as an existing command I had changed the meaning of the
word OPEN() so how was 
the error message incorrect?

snip....
> 
> My impression has always been that fptech's corporate opinion of our
> idea, going back at least three owners now, was roughly equivalent to
> John's.  Ken, Wally and Bud are all listening here.  If they think the
> ideas are useful no doubt they can find a way to use them.

They do not monitor the list except occasionally.  Do not expect
postings here 
to be added to the bug reports or gain consideration.
> 
> Alas, there are many thinsg that remain broke... and ain't gettin fixed.

And again I ask if the problem is a bug - have you reported it
correctly.  If it is something
you think has been omitted or is lacking, add it to the wish list.  Make
you voice heard 
correctly and it will help us all by improving the product and keeping
you happy.

Nancy
-- 
Nancy Palmquist 
Virtual Software Systems
PHONE: (412) 835-9417			Web site:  http://www.vss3.com