[EpiData-list] Epidata Manager key unique handling

epidata-list at lists.umanitoba.ca epidata-list at lists.umanitoba.ca
Mon Sep 15 10:13:11 CDT 2014


Hi Rasool,

I had a look at your file (thanks for sending it). Here is the problem - something for the development team to address.

Problem: The key field is a calculated field, based on 3 other must enter fields and it is no-enter. Because the user does not enter this field, it’s uniqueness is only checked at the time when the record is being saved. Then you cannot save the record, as you will have seen. Problem 2: the user is not told that there is a duplicate key; the record just cannot be saved.

Workaround: Put the key field in a position immediately following the 3 fields used to calculate the field. Turn off NO ENTER and ask the users to NOT change this field. When the user hits the <enter> key, the duplicate is identified.

Solution for the long term: Entry Client should check whether a calculated field is KEY and if it is, then the check for duplicate should be performed when the field is calculated.

Note to  Jens & Torsten: The same problem arises, if the 3 fields are declared KEY, rather than calculating the key. The only time the uniqueness of the resulting key is checked is when the record is saved. Solution: after entry of each of the fields declared key, check to see if all the keys have been entered and then perform the check for uniqueness.

Jamie

On Sep 13, 2014, at 4:18 PM, epidata-list at lists.umanitoba.ca wrote:

> I have done that but during data entry it is not stoping on duplicate ID entry. At the end of last field entry it is not moving for second record.
> 
> Thanks,
> Rasool Bux
> 
> epidata-list at lists.umanitoba.ca wrote:
> 
> All you have to do, is to define a key, which you find under project properties. After definition of a key,  only one observation can be entered for each value.
> 
> In entryclient a key is always what was "key unique" in Classic Epidata 3.1.
> 
> Regards Jens Lauritsen
> 
> epidata-list at lists.umanitoba.ca skrev:
> 
>> Dear all,
>> 
>> I have tried to use epidata manager & client. The Entry client is not indicating on duplicate entry of id field as in Epi data classic 3.1. Please let me know if there is any option to give message just after entering the key field and stop the entry to next fields.
>> 
>> Thanks & best regards,
>> Rasool Bux
>> 
>> ________________________________
>> 
>> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
>> _______________________________________________
>> EpiData-list mailing list
>> EpiData-list at lists.umanitoba.ca
>> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
> 
> ________________________________
> 
> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
> _______________________________________________
> EpiData-list mailing list
> EpiData-list at lists.umanitoba.ca
> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
> 



More information about the EpiData-list mailing list