Re: How to verify if the current value entering exists on the database

** Kelly, I followed instruction # 2 however, the lastcount is counting all the records that areon the form instead of only values that matched the current value. Any recommendation?Kelly Deaver [EMAIL PROTECTED] wrote: ** There are several ways, depending on what you are trying to accomplish.

Re: How to verify if the current value entering exists on the database

** Why make it so complicated Filter 1: ( 'TR.field' != 'DB.field') AND ( 'TR.field' != $NULL$ ) Action, set field, 'field' = $field$ to a tmp field, use first matching request, else set to null Filter 2: Check if the tmp field is null or not, and give an errormessage if not null. L

Re: How to verify if the current value entering exists on the database

I was thinking more basic/fundamental. Filters support TR. field name prefixes for specifically this purpose. It's the transaction value (vs. DB. or database value). If TR. value is not null, it's been changed (i.e. different from the database value). In your example, your Run If would include

Re: How to verify if the current value entering exists on the database

Hi, Just for the record... The following qualification does not verify that a field has been changed: ('TR.field' != 'DB.field' AND 'TR.field' != $NULL$) You should rather use something like this: ('field' != 'DB.field') If you like to perform the check only if the field has been changed to

Re: How to verify if the current value entering exists on the database

** Misi, You beat me to it. :-) I think the common misconception here is the belief that the TR value will have a value only if the field changed, which isn't true. If the field is part of a push fields action, then TR.field will have a value regardless if it has changed or not. You can see

Re: How to verify if the current value entering exists on the database

I guess that you can use the TR-value if you like, but is usually not required. You could use either of these syntaxes with the same result: ('field' != 'DB.filed' AND 'field' != $NULL$) ('field' != 'DB.filed' AND 'TR.field' != $NULL$) Depending on what client and version you are useing, fields

Re: How to verify if the current value entering exists on the database

** I first learned about the TR.field having a value in a push fields during a PTT class, and always accepted it, but had never fully investigated it (via SQL logs) until just before I posted, so yeah, I did check it. Some other things to keep in mind... When ARS gets the DB value it is using

Fwd: How to verify if the current value entering exists on the database

** Thank you all, you guys are great help!!!Jerry, I think you confused me with somebody else.God blessNote: forwarded message attached. All-new Yahoo! Mail - Fire up a more powerful email and get things done faster. __20060125___This posting was submitted with

How to verify if the current value entering exists on the database

** Can anybody help me how can I check if the current value entering already exists on the database?Thanks in advance for your help All-new Yahoo! Mail - Fire up a more powerful email and get things done faster. __20060125___This posting was submitted with HTML in it___

Re: How to verify if the current value entering exists on the database

** There are several ways, depending on what you are trying to accomplish. I'm going to call the field you are interested in FieldA in my examples. 1. If you are trying to assure that no two records have the same value in a particular field (FieldA), create a unique index for that field. In the