TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Melonie wrote on 5/13/96:
>The majority says stay with relational database
>terminology (rows and columns). I think I will
>do this with ALOT of explanation for our readers.
>One more question--the single block formed by
>an intersection of a row and a column, in a Word
>or Frame table this is called a cell. However, the
>programmers tell me you call both this single block
>and the column a "column". That, I know, will not
>fly with my readers.
If you properly explain rows and columns (most everyone is familiar with
tables) to your readers then calling the intersection a column should not
really be confusing. Actually, you are not calling the intersection a column.
It may seem that you are because you are discussing one row at a time. If you
were discussing one column at a time, you would call the intersection a row.
Just think of it as a one row table. Since you have already decided to use
relational terminology, I would use "column" and not introduce additional
Cincinnati Bell Information Systems, Inc. (CBIS)
chuck -dot- blessing -at- cbis -dot- com
- OR -
cjb -at- one -dot- net
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net