RE: Strange effect of conditioning DSPF fields

Hi Booth

There was a complete blank line between the two fields, so I don't think
it's that. I just noticed though, that the positioning of the blank (9/78)
overlaps the COMMENT field which is 9/30 to 9/79.

Thanks

Jonathan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: 10 July 2007 16:36
To: Midrange Systems Technical Discussion
Subject: Re: Strange effect of conditioning DSPF fields

YOu mentioned that when you placed a blank between the fields the
problem also went away? Is this because you need an apparently blank
space to hold the attribute character> That doesn't really make sense
to me because that would be a leading space, not a trailing space.
However I suspect that the blank is somehow related, since that changes
the behavior?



Jonathan Mason wrote:

Hi Joe

The TEXT field is defined in the field reference file as:

A TEXT 50A TEXT('Text')
A COLHDG('Text')

In the display file DDS I tried coding COMMENT as 50 and 50A, but neither
made any difference.

Thanks

Jonathan


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: 10 July 2007 16:01
To: 'Midrange Systems Technical Discussion'
Subject: RE: Strange effect of conditioning DSPF fields

From: Jonathan Mason

For example, in the sample DDS below the COMMENT field doesn't allow

lower

case entry even though CHECK(LC) is defined.


A COMMENT R B 9 30REFFLD(TEXT)

A N33 COLOR(WHT)

A 33 COLOR(RED)

A 33 DSPATR(PC)

A CHECK(LC)

Jonathan, what's the DDS definition of the TEXT field? Does it contain a
shift code or something?

Joe