[T24]: E ETEXT ERR STORE.END.ERROR

[Jane]

Could anyone tell me when ERR should be used? And when
STORE.END.ERROR ?

My understanding is that STORE.END.ERROR (ETEXT) should be used in
validate routine or input routine while ERR (E) in authorise routine .
Is that correct?

If both are called in the same input routine, will they cause any
messed up?

It is my first post in this group :-)
Any feedback will be appreciated.

[Gayathri Ramakrishnan]

Hi,

 

   ERR routine is used to present the error to the user one by one. On the contrary STORE.END.ERROR will store all the error occurrence with in a transaction boundary and throw them to the user in a single shot.

    This is the reason why we call STORE.END.ERROR during cross validation and ERR during check fields validation.

  After the introduction of BROWSER, the concept of validation at check fields level has diminished a lot. But still its available in certain fields of the template with the concept of hot validation (even at version level).

 

Cheers,

Gayathri

2009/4/8 Jane <helloh...@gmail.com>

--
Regards
Gayathri

[丁晓平]

Jane,

In normal development you just need to call STORE.END.ERROR; routine ERR
is used print out the message in variable "E", which is used in standard
template.
It is supposed that during authorization stage there is no business
checking so the STORE.END.ERROR(ETEXT) will be suppressed by the system,
however if you do want to quit then just specify the value in "E" and then
the template will call ERR and quit.
For t24 related issues you can deploy in another group
"t2...@googlegroups.com".

DD

-----邮件原件-----
发件人: jB...@googlegroups.com [mailto:jB...@googlegroups.com] 代表 Jane
发送时间: 2009年4月8日 23:51
收件人: jBASE
主题: [T24]: E ETEXT ERR STORE.END.ERROR

[Jim Idle]

> -----邮件原件-----
> 发件人: jB...@googlegroups.com [mailto:jB...@googlegroups.com] 代表 Jane
> 发送时间: 2009年4月8日 23:51
> 收件人: jBASE
> 主题: [T24]: E ETEXT ERR STORE.END.ERROR
>
>

All,

Can we please post to the group in UTF-8 encoding and not GB2132 or
Big5. Many people will not have the latter encodings available, but all
clients will deal with UTF-8 these days.

Thanks,

Jim