Hi Freaks
It seems to me that whith every new UnifAce-Version the behavior of DISCARD change
If the DISCARD in the READ-trigger itself the UnifAce engine
a) recall the READ-trigger (very old Uniface versions, result sometime to an stack overflow)
b) starts the READ-trigger again (current UnifAce versions)
But we do have a globale procedure to execute the read.
In this case UnifAce
a) steps to the next statement (if then is no more to read)
b) leaves all procedures and return to the READ-trigger
c) restart the current procedure. Sic! (with 10.4.3.032?)
[i.e. cleans all variables and starts the procedure just at the begin.]
I’m not sure with which version the behavior change from b) to c) or if there was other “reaction” in between
Testing our product under UF10.4.03.32 leads to crashes when retrieving and/or sorting hitlist with rows to discard (due to right managament)
The same routines in the old environment works perfect.
Does some else do have DISCARDS in subroutines (called direct or indierect from the READ-trigger)?
Do you have also “problems” when retrieving/sorting hitlist?
@UnifAce: Did there something change how UnifAce handels DISCARDS?
Ingo
