Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Conversion of Defined Fields to More Restrictive Types

IP.com Disclosure Number: IPCOM000046954D
Original Publication Date: 1983-Sep-01
Included in the Prior Art Database: 2005-Feb-07
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Chang, PY: AUTHOR

Abstract

In the revise descriptor task of a word processing application, the user has been able to change the field types to a less restrictive type, such as arithmetic to character, character to text, or arithmetic to text, but the system does not allow the user to change the field types to more restrictive types, such as text to arithmetic, text to character, or character to arithmetic. This restriction was imposed because some data records may have data that does not meet the criteria of the more restrictive field types. There are, however, several conditions under which the user might want to change the field to a more restrictive type: 1) The user simply made a mistake. For example, the user may have typed the command for a character field instead of for an arithmetic field when he was defining the field.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 57% of the total text.

Page 1 of 1

Conversion of Defined Fields to More Restrictive Types

In the revise descriptor task of a word processing application, the user has been able to change the field types to a less restrictive type, such as arithmetic to character, character to text, or arithmetic to text, but the system does not allow the user to change the field types to more restrictive types, such as text to arithmetic, text to character, or character to arithmetic. This restriction was imposed because some data records may have data that does not meet the criteria of the more restrictive field types. There are, however, several conditions under which the user might want to change the field to a more restrictive type: 1) The user simply made a mistake. For example, the user may have typed the command for a character field instead of for an arithmetic field when he was defining the field. If the user has previously defined many other fields, he will not want to redo the entire thing in order to correct one mistake. 2) The requirement has changed. A field may originally be defined as a character field to anticipate some nonnumerical data, but later it may be necessary to perform arithmetic operations on it.

In this case, the character type needs to be changed to an arithmetic type. 3) If an input/output error happens at the beginning portion of a file, the file recovery task will regenerate the field descriptors that are lost. All field types are assumed to be text types; therefore, there may be a...