Reject user from SQL-DB

[JB]

>> Return:
>>
>> attr = 'Auth-Type'
>> op = ':='
>> value = 'Reject'
>
> Of course! How embarrassing. ;-)
> I actually tried that before but during the reply-items-query which  
> has no effect. Returning Auth-Type := Reject from the check-items- 
> query does the trick. Makes sense, doesn't it?

Ok, now I'm returning Auth-Type := Reject from my check-items-query  
and I hoped to be able to send a little more in depth information  
along the way in the Reply-Message attribute, but unfortunately this  
info gets lost. It seems that I have to fill this attribute in the  
reply-items-query.

Does this mean the reply-items-query has to trigger the same functions  
as the check-items-query again to find out what the reason for the  
reject was? Or do I have to fill a temporary table with the reply  
message in the check-items-query which gets then returned in the reply- 
items-query?

I guess there is a much better way without unnecessary database load.  
What's the common practice here? Is there a control attribute which  
can be used for internal communication among these queries?

Thank you!
JB