>>>So it does not matter what I name it
>
>I think that names matter a lot.
>Many of the programming errors I make or uncover can be attributed to faulty naming of procedures or variables. Good naming, on the other hand, makes maintenance a lot easier.
>
>As far as this problem is concerned, I typically add a character field that indicates the status of the item. In this case it would be named partstatus and "A" would be active and "I" would be inactive. The use of characters allows for more choices, should they become necessary.
>A part could be not yet active because some event, such as QC approval, has not occurred, or it could be obsolete.
>Using a character type allows that distinction if needed.
I have changed my mind and decided to go with your suggestion; a character 1 len type.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
