Why?

[Brian K. White]

> From: Kenneth Brody [mailto:kenbrody at bestweb.net]
>
> And when you get 5.0.14 and the bug is still there, because fPTech
> does not have the ability to duplicate the problem, what then?


George Simon wrote:
> I'll do what I'm doing now, calling the table from elsewhere.

Beleive it or not, I think most of us would be grateful if you would help
finish tracking this down.
There may be a bug, and it may be perfectly fixable, and it just needs
someone to have uncovered it.
Obviously your process can be written to avoid the problem, and obviously
none of the rest of us _seems_ to be hitting the same problem, but then
again, maybe we _are_ but it's just been too obscure and rare for anyone to
identify the pattern as well as you already have. I hit things all the time
that I think should work, but don't, and I do it some other way and move on.
Who know how many of those are actual bugs that really should be fixed vs
how many are just me not playing by the rules?

I don't like the thought that my filepro may have hidden bugs waiting for me
to hit. That is one reason I went to the bother or trying to duplicate the
test.

You have already done what was going to be my next test, so I won't now. But
given any further info or reason I will help test some more.

It's a bother, but what the heck? We've already put this much time into it,
why not put a little more in and at least get something back out of it?
Right now, if it stops here, the time was wasted. Even if the outcome is we
establish that there is no bug because we found programming that according
to all the rules is not supposed to work exactly that way, that is almost as
productive as fixing a bug. Maybe more, because now, maybe some people are
going to be paranoid about using call tables from auto processing and make
life harder for themselves avoiding using a feature for no reason.

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani