Hi all,

I am developing a business administration system and have problems validating a value. When a script runs, it opens a custom message that requests a value. The value should be unique, so I want to test it. As the field definition already requires it to be unique, I planned to use the ErrorCapture to catch the invalid non-unique value (error code 504 - value is not unique as required by field definition), but it doesn't. Only when the script has ended and a record has been created, do I get the standard system message saying that the field requires a unique value. This is too late. Anyone any idea how to solve this prob?

Thanx in advance,

Chavito - The Netherlands

Hi all,

I am developing a business administration system and have problems validating a value. When a script runs, it opens a custom message that requests a value. The value should be unique, so I want to test it. As the field definition already requires it to be unique, I planned to use the ErrorCapture to catch the invalid non-unique value (error code 504 - value is not unique as required by field definition), but it doesn't. Only when the script has ended and a record has been created, do I get the standard system message saying that the field requires a unique value. This is too late. Anyone any idea how to solve this prob?

Thanx in advance,

Chavito - The Netherlands

Hi all,

I am developing a business administration system and have problems validating a value. When a script runs, it opens a custom message that requests a value. The value should be unique, so I want to test it. As the field definition already requires it to be unique, I planned to use the ErrorCapture to catch the invalid non-unique value (error code 504 - value is not unique as required by field definition), but it doesn't. Only when the script has ended and a record has been created, do I get the standard system message saying that the field requires a unique value. This is too late. Anyone any idea how to solve this prob?

Thanx in advance,

Chavito - The Netherlands

Opdrachten.pdf

Try commiting the record with an Exit Record script step after the Show Custom Dialog steps. You may also need to set the error to a global and use that for your error trapping since you have those other steps in the loop.

Try commiting the record with an Exit Record script step after the Show Custom Dialog steps. You may also need to set the error to a global and use that for your error trapping since you have those other steps in the loop.

Try commiting the record with an Exit Record script step after the Show Custom Dialog steps. You may also need to set the error to a global and use that for your error trapping since you have those other steps in the loop.

Thanx, I'll give it a try.

Thanx, I'll give it a try.

Thanx, I'll give it a try.

Thanx Ender, I moved the ErrorCapture[ON] into the loop, put in a GotoField[next] step just after that and right before the If(status) expression and it works like charm. As easy as that.

Thanx Ender, I moved the ErrorCapture[ON] into the loop, put in a GotoField[next] step just after that and right before the If(status) expression and it works like charm. As easy as that.

Thanx Ender, I moved the ErrorCapture[ON] into the loop, put in a GotoField[next] step just after that and right before the If(status) expression and it works like charm. As easy as that.