Modifying real fields in automatic (was Re: Some Sort of ControlFrom The Browse Screen)

[flowersoft at compuserve.com]

Not that I don't want you to have the last word John, but...

>If you are going to use a special processing table in the first place, why
not just write an absolutely perfect, full >blown process that lets you use
any key to modify the browse, with complete control, and all the features
and functions >of processing available to you?  The right way to do this job
is with a processing browse, period.

You seem to read and/or quote my posts selectively.  Did you miss the one
where I said to Ken:

"Understand that I'm not advocating that it is OK to update real fields in
automatic processing, just like I never advocated using "write" in automatic
processing, although I did find it necessary to use it in one case to be
able to accomplish what was needed.

"If I was tackling this problem I would have used the method you originally
recommended, which was to do a browse lookup from the main file and handle
it with processing.  Much cleaner, but that is not the solution he was
asking for."

"He wanted a solution that would work from the regular browse screen and
that is what I tried to give him."  

>Oh, and as for only people using the -y myauto changing the value... What
do
>you think I meant?  Two people using normal processing?  :-)  I meant
>everyone involved using your processing, do you want to state which person
>will see the correct value or not in that case? That is the only scenario
>that matters in this discussion, no?

You got me there. I must admit that during those 15 minutes I did not
anticipate that two or more individuals might be checking off the items that
have cleared from the same checking account at the same time. 
However, if that were to be the case, my code would still work because the
tree doesn't really fall unless the user presses "U". :-)