You are much better pre-coding your data on the data collection form. I would start by pre-coding the categories you want, and then do a pilot to see if any other common categories occur. 

You can run into trouble coding after the event.

1. It takes far longer than coding at the time

2. It is best to code "live", when you can follow-up or clarify incomplete or vague responses. After the data are collected you have a much reduced opportunity to do so.

For example, I worked with data where occupation included "Works for the city corporation" and "Operative". These responses were uncodable (both the street sweeper and the Lord Mayor work for the city corporation, and there was no way of knowing what the operative operated.) Pre-coding occupation would have meant that the interviewer could have clarified the person's job at the time of data collection.

A pilot is very useful to see if there are categories you didn't anticipate. But I would sooner run a pilot than have to hand-code an "other" category afterwards.

Think forward to your final report. What categories will you be using to report on your data? Use these categories, and don't be tempted to collect excessive detail or data you don't need.

Dear Mr. Conroy, Thankyou for the respone, appreciated. I am afraid though, that i put up the question in a wrong way, maybe, as I have already pre-coded responses in my paper data collection form, at the moment i want to enter that data into epi-info via the create form function, here-in lies my problem, while designing the forms, do i put in the responses as it is i.e. text form, or do i just design the form with only numbered codes for responses e.g. 1 for no education, 2 for secondary education and so on ?

Use coded data for statistical analysis, using EpiInfo or other package, and assign proper labels later.

It will work best with a very small variable label at the top of each column field.  Personally, I found that a three-letter 'code' that was recognizable to the person entering the data or doing the analysis, reduced time wasted by looking up the numerical code in your 'code-list'. Three letters maximum!

You should better have a data dictionary with coding numbers for answers and coding labels for better data entering. You should do this ahead of time before collecting your data, piloting your questionnaire is also advisable, I would not delay the coding or enter data into any statistical software before having a data coding dictionary.

Thank you Gentlemen for your responses, these were helpful.

Yes you need to develop codes for the questions with small number of categories in your questionnaire so you can have a space for the codes, otherwise you can leave the questions that have many possibilities for answer e.g. the Governorate of residence or district or locality but you need to develop the list in your epiinfo dropdown list. You may add other categories to your data screen without losing your entered data, but if you want to change the type of variable e.g. from test to number format you have to delete the table that contains all your entered data. I advice you to use numbers in your coding system for accuracy  and simplicity during data entry, later when you start your data analysis you can easily change the number codes to test in excel.

It is better to give codes to the answers so that later on you can be safe from trouble however you can add/give codes to any new response arised in the interview

It's a little awkward in Epi Info to add a new variable after the date are entered.  It can be done but the easiest way is to create an extra two or three variables - give them variable names or codes xx1, xx2, etc.  If they are not needed, they remain empty; if you need to add a new variable while entering the data, you can use one of these.