>>>>>If you wanted to use a non-technical term for field types: Integer, Decimal, Boolean? I guess Decimal should be understood by a non-technical person. But I would prefer to find 'better' words for 'Integer" and 'Boolean'
>>>>
>>>>If the document is technical, I would use those fields as is. The latest one were about a SQL Server backend, so I used those SQL Server related field type terminologies. If it is about code, than specific coding environment might do. You can still provide some explanations and examples so a non technical users would have an idea of what's in it.
>>>
>>>It will be kind of a technical document but to be used by an end user. So maybe calling non-technical document would be more appropriate.
>>
>>In such cases the users generally don't even bother with fields, they think in terms of GUI, so for them it's a checkbox (or tickbox in the UK, dunno why they prefer that). If you must describe a table, well, a "yes/no" is the description I used often and had no complaints.
>
>In this specific case I am creating a tool that will allow user to define/set all fields of a form. And he/she will have to specify what type they want to use for this or that control. They will have a drop-down list of various types. So the drop-down will have "Whole Number, Decimal Number, Yes/No, etc." Otherwise, it would have to be "Integer, Decimal, Boolean".

Then the user has to know that some values like moneteray ones, are really (long) integer type for better accuracy. Perhaps rethink ;-)