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

Kenneth Brody kenbrody at spamcop.net
Wed Oct 20 20:19:04 PDT 2010


On 10/20/2010 5:16 PM, flowersoft at compuserve.com wrote:
> I didn't put it in input processing because I didn't want other users to be
> affected by the code

And putting it in automatic won't affect other users?

> and still wanted the user toggling field 5 to be able
> to actually modify other parts of the record if he/she wanted to.  I was
> doing that by allowing the user to hit "break" from the browse and then put
> them on screen 1.

You still haven't given any reason why you can't put it in input, where it 
belongs, rather than automatic.

> Since you can only detect @sk="brky" from automatic when not at an input
> statement,

Huh?

> that's where I put the 3 lines of code.  No one will ever be
> affected by those 3 lines of code except that user.  In input processing,
> everyone would have been exposed to the code and I would not have been able
> to take the user out of the browse and unto screen 1 by trapping the break
> key.

I don't follow.  What, exactly, do you want to do if the user presses Break 
that you "can't do" if the assignment to field 5 is in input?

> Maybe I could have found ways to do all this from input but I only spent 15
> minutes or so coming up with the code.  At that time, I didn't want to make
> it my life's work, I just wanted to give him a quick solution to the problem
> he was facing without asking him to use a totally different method or just
> that it could not be done.
>
> Your argument is that it is wrong because it is just wrong to assign values
> to real fields from automatic processing in general.  That's like saying
> that guns are bad because they kill people.

Actually, I think it's more like saying "don't point a loaded gun at a 
person, even if you don't plan on pulling the trigger".

>  My argument is that yes, maybe
> guns are bad because they kill people but you prove otherwise, in this
> particular case the gun is not loaded and the safety is "on". :-)

I think you loaded the gun and the safety is off, and you're hoping that no 
one drops it.

[...]

-- 
Kenneth Brody


More information about the Filepro-list mailing list