Hi,
<db:dbform
followUp="<%=followUp%>"
followUpOnError="<%=followUpOnError%>"
tableName="COMMANDE"
whereClause="<%=whereClause%>"
maxRows="1"
--> overrideFieldCheck ="true"
redisplayFieldsOnError="true"
_javascript_FieldsArray="true"
formValidatorName="commande"
_javascript_Validation="true"
>
Is it an order for the db tag : overrideFieldCheck in the dbform tag.
Like this , it doesn't call Interceptor ?
Thanks
-----Message d'origine-----
De : Shawn [mailto:[EMAIL PROTECTED]]
Envoyé : lundi 4 octobre 2004 19:20
À : [EMAIL PROTECTED]
Cc : dbf
Objet : Re: [dbforms] Bug in Interceptor with input type in fields
> Hi ,
>
> I have come to realize that in the newer versions of Dbforms:
>
> If no (dbForms) input fields have been modified by the user, the form
> is not processed (validator is not invoked) when submitted. This is a
> good optimization however for
>
> Backwards compatibility, it would be necessary to still allow a call
> to the interceptor method. This could be implemented via an extra
> parameter (forceSubmit)?
use overrideFieldCheck in the dbforms tag
If set to true the field values will not be checked if they are changed. The database update will be done always This could be usefull if you want to call your interceptor always to check fields which are not part of the table. In your interceptor you can use return DbEventInterceptor.IGNORE_OPERATION if you do not want the database update
[RTExpValue]
--
Shawn <[EMAIL PROTECTED]>
