Hello,
When exporting to Stata (ver13), value labels don't seem to follow the
data. We are using Epidata Manager 2.0.5.51 and first I thought it was due
to value labels being external rather than internal, but then I tried with
a dataset with internal value labels, but the result was just the same, no
value labels visible in Stata.
Help much appreciated!
Pekka Isosomppi
It works perfectly with the latest version.
Thank you so much.
Kind regards,
Suparee Boonmanunt
> ------------------------------
>
> Message: 2
> Date: Thu, 09 Jul 2015 11:35:51 +0200
> From: EpiData development and support
> <epidata-list(a)lists.umanitoba.ca>
> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca>
> Subject: Re: [EpiData-list] Access violation when comparing duplicate
> files
> Message-ID: <B3DDB8E1-29FF-4F06-A0FD-91B376D68C46(a)epidata.dk>
> Content-Type: text/plain; charset=UTF-8
>
> Please dowload latest version which is 2.0.5.51, you have used a previous version.
>
> Try again and inform here if it works.
> Regards jens Lauritsen
> Epidata association
>
> ------------------------------
>
> ________________________________________
> EpiData-list(a)lists.umanitoba.ca
> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
> End of EpiData-list Digest, Vol 140, Issue 5
> ********************************************
Thank you for your reply
1. I use version 2.0.4.43 for Mac
Program Version: 2.0.4.43 r1156
Core version: 2.0.0.0 r1161
FPC Version: 2.6.4
Platform: i386-Darwin
2. Both dataforms have the same identical 10 sections. I have created 1 dataform with 10 sections and let 2 people insert data parallel.
3. I haven’t defined any key, but I have defined an ID as a variable for each subject. However, it is not used for coupling the two files.
This is what I did:
Document -> Compare duplicate files -> (the new window pops up) -> Click on “Compare” -> Click on “Add files” -> select those 2 files -> select the sections I would like to compare
Thank you so much.
Suparee Boonmanunt
>
> ------------------------------
>
> Message: 2
> Date: Wed, 08 Jul 2015 12:20:51 +0200
> From: EpiData development and support
> <epidata-list(a)lists.umanitoba.ca>
> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca>
> Subject: Re: [EpiData-list] Access violation when comparing duplicate
> files
> Message-ID: <88C2E6EF-3317-4256-81A5-212A9B9228BF(a)epidata.dk>
> Content-Type: text/plain; charset=UTF-8
>
> Please inform us of:
> 1 the version of manager You are using.
> 2 are you working with sections on one dataform or a related system with fields and sections on all dataforms
> 3 have you defined a key, and if so is that used for coupling of the two project files?
>
> You get the version from the help menu "copy version "
>
> /Jens Lauritsen, Epidata association.
>
> On 8. jul. 2015 12.09.45 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote:
>> Dear all,
>>
>> I am trying to compare the duplicate files. I did it for each section.
>> In some sections with small number of fields and just integer, the
>> comparison goes well. But in other sections with larger number of
>> fields, the program always shows the message ?Access violation? and ask
>> whether I will ignore it and continue and kill the program.
>> I always choose to ignore and the program seems to work on something.
>> But nothing has really happened.
>>
>> Should I just wait, because the program is still working? Or should I
>> fix something in the entries?
>>
>> I would be very grateful if someone could suggest me what to do.
>>
>> Kind regards,
>> Suparee
>> _______________________________________________
>> EpiData-list mailing list
>> EpiData-list(a)lists.umanitoba.ca
>> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
> ------------------------------
>
> ________________________________________
> EpiData-list(a)lists.umanitoba.ca
> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
> End of EpiData-list Digest, Vol 140, Issue 4
> ********************************************
Dear all,
I am trying to compare the duplicate files. I did it for each section. In some sections with small number of fields and just integer, the comparison goes well. But in other sections with larger number of fields, the program always shows the message “Access violation” and ask whether I will ignore it and continue and kill the program.
I always choose to ignore and the program seems to work on something. But nothing has really happened.
Should I just wait, because the program is still working? Or should I fix something in the entries?
I would be very grateful if someone could suggest me what to do.
Kind regards,
Suparee
In a specific project where we wanted to enter one field extra following extract and import of hospital records the following two problems emerged. Both aspects will be fixed in August. Just now there is a pause in development until August.
Be reassured that we do all we can to solve such issues since they are in essense what we call "show stoppers" of using the software - unless we manage to find and fix the cause. Which we - expressed with modesty - have done until now. Apart from a special issue in estimation of certain lifetables in EpiData Analysis. But for that one have decided to fix it as part of the rewriting of the software to the "epx based" standa
The current two issues relates to: EpiData Entry Client
Program Version: 2.0.3.15 r481, Core version: 2.0.0.0 r1161, FPC Version: 2.6.4, Platform: i386-Win32
1. Lack of "value changed" upon entry in existing field with currently no information in that field
Normally when you use the value label box (F9) to select values and change a value, then the current record is marked internally as edited. Upon change to the next record the system should ask "save record".
But apparently this does not happen, the EntryClient just moves to the next record without saving the value
2. The standard behaviour of EpiData software when a user moves a given window to a new "non-default" position is that next time that window is opened it will be placed in that same position.
This is currently not the done with EntryClient for the value label box and the "confirm change to records" box.
The remedy until fixed was the following:
I added an integer field of length 1. Then I changed the range to 1-1 and added mustenter requirement. In other words the only possible entry is a 1 (one).
This shows that sometimes combinations of attributes can give problems, which we - unfortunately - have not identified yet. When we see such situations they are then added to the list of structured testing, which we apply before public release. The list is increasing with increased number of handled special situations.
The solution could only be identified by a structured "trial and error" process, where I managed to find the cause, which can then be remedied.
Unfortunately in some situations it is very difficult to create such a process. In particular when an issue is only present in some versions. An example of this is the 32/64 bit windows v8.1 issue which have struck some users and another issue where we have seen that a given epx related file works very well in Linux and Mac, but in Windows 7 creates an access violation on attempt to edit an existing record. .
Any structured input to solving such problems is highly welcomed.
Regards
Jens Lauritsen
EpiData Association
Denmark.