Some Info about fms udf values....

[Former Member]

see the image...

Normally we are entering some values in to the udf values..

it will accept duplicate values all so

My requirement is it possible to restrict the duplicate values at the time of creation...

[edy_simon]

Hi,

In your formatted search query, use grouping.

SELECT DocDate From ORDR GROUP BY DocDate

Regards

Edy

[vijay_rajkumar]

You can use Transaction Notifications, or if your having an Add-On, you can code it in the Add-On.

[edy_simon]

Hi,

I misunderstood your question.

Yes you can block duplicate values.

Just go to User Defined Field - Management,

Click on your UDT, and click on Keys.

Create a new key for your field.

And Check on the Unique check box.

Regards

Edy

[Former Member]

KK I Will check it..

[vijay_rajkumar]

Keys is also a good feature, forgot about it.

[Former Member]

Hi,

Sir

Sorry For the late..

I had not checked this reply..

i had seen but i had tried bcz , little bit busy..

now i have a look on this post..

+++++++++++++++
in emp master i created a udf value..

I am trying to update the value...

but one error message is comming.. like

[Microsoft][SQL Server Native Client 10.0][SQL Server]The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.OHEM' and the index name 'OHEMIX_0'. The duplicate key value is  'User Key Description' (OUKD) (<NULL>).

if i see in the sql 22 null records are there..

how can i implement this one..

my requirement is in fms second option is there

Search in Existing User-Defined Values

i don't want to give the chance to the user for entering the duplicate values..

[edy_simon]

Hi,

Quoted : "

[Microsoft][SQL Server Native Client 10.0][SQL Server]The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.OHEM' and the index name 'OHEMIX_0'. The duplicate key value is  'User Key Description' (OUKD) (<NULL>).

if i see in the sql 22 null records are there.. "

If you are not allowing duplicate value, then you should clean up your old data first isn't it ?

Just update them so they contains no Null records and Unique.

"

my requirement is in fms second option is there

Search in Existing User-Defined Values

i don't want to give the chance to the user for entering the duplicate values.."

There is no way you can stop user to enter a duplicate value with using FMS alone.

Even using programming, you can never stop two user keying in the same value at the same time (Before the records were added)

You can only block the user from adding the record when there is a duplicate value in the Database.

Regards

Edy

[Former Member]

Hi,

Sir..

One Thing i understood..

fms values i cant not stop if the person enter duplicate values...not in the db in the field ..

before adding..

but i can check it before adding perss  1 button..

actually i started this reply for solving the duplicate values..

now i realized it is not possible to stop it...

Thank u for your reply..

Keep posting..

[vijay_rajkumar]

Hi Edy,

True you cannot stop 2 people from entering the same data at the same time.

However, if your having a code to validate this data just before adding the data to the database, it's good enough to prevent this problem to almost 99%.

The probability of 2 people entering the same data at the same time where the same time being just a fraction of time in which the validation has to be run is mostly improbable. Especially for an SME solution where number of people using the system cannot exceed a 100 at a given point of time.

So I'm guessing the solution is fine..

Thanks,

Vijay

[edy_simon]

Hi Vijay, I wouldnt count on the 99%. Aside from no of users, volume of trans also count. I have experienced where 5 users keying in up to 10 thousand records in 3-4 days every mid month and end month. Actually, they are still now. And believe me that 1% will give you enough headache!  But, i agree with you if you are expecting less user and trans, code is enough. For me,  SP notification / Unique key field is the best for my situation. Regards, Edy

[Former Member]

Hi,

     Are you using UDT? Normally, if you are using UDT. It will not accept duplicate in Code field. So, put your value in Code field from your UDT.

Regards,