>I am getting an application documented and would like to standardise on the terms been used. I have seen a Form described as a Window, a Screen and at other times a Form.
>
>I have also noticed that Edit Boxes and List Boxes are also sometimes called Windows or Edit Window or List box Window. Here I think it should be clearly called a Box and not a Window.
>
>However I would like some advice on what is standard terminology for a Form in "User Documentation"

Here's a brief rundown from my experience documenting here: We had a team here (I was on it) that spent a year drawing up standardized bureaucratic conventions (Boy was that a fun team! :) for what to call things using different software VFP, VB, PB, Access, etc.

First, we use different terminologies depending on who the docs are written for. For developer docs, we stick with the individual development-tool terms like Form, Combo, Option Button, Command Button, DataWindow for PB, Grid for vfp, Pageframe for vfp, Tabset for PB/VB, etc.

For user procedural or Help docs, we never use Form - always Screen or Window (those are interchangable). Pageframe is a tough one since that is not standardized well. We call them "Pageframes" or "Tabsets" (as a container), or "page" or "tab" as an object. Grid is tough too - we just call those "Lists" usually in the user docs. A combo is a "dropdown list," a listbox is simply a listbox or list. Checkbox and Toolbar are fine as is, Option Group is still usually called Radio Group/Button, since most everyone was familiar with that term for user docs. An Edit or Listbox is *not* a window to a user, it is simply a control or object.

The upshot is, you may want to form a small team to standardize your terminology. If you don't, you can get a very large mess of different docs, making it very hard for users to understand. MS has some standard object references at their site (though thet are continually changing), worth looking at to get some ideas.