When working with files in windows there is no difference btw. "chk" and "CHK" as extension for a file, however in Linux (possibly also in MAC) there is a difference. This is also relevant for EPX versus epx.

It turns out that apparently the new batch processor "epidatacmd" can give problems when creating files due to problems of "EPX" versus "epx" extensions. WHen using these files on a Linux pc a file with the name myfile.EPX will not show up on the "supported files", list in manager or client.

Other issues when working with the latest released Manager and EntryClient I have found are: a. Sometimes "access violation" occurs when I change the setting in Manager of "showing variable names" or not.

b. Sometimes single files created from templates with the epidatacmd processor and subsequently combined in the Manager with "import structure" cannot be read by EpiDataClient.

These errors will be fixed - these are examples of why testing is important on the path to the first public release.

An updated Analysis (build 175) has been placed on the http://epidata.dk/testing.php. The only change is adaptation of reading epx files with the most recent changes to the epx structure.

regards

Jens Lauritsen EpiData Association .....................................................................................