Conference iosg::all-in-1_v30

Note:

/RSE_RECOG=CAL$CALENDAR.FILLER WITH
 .FILLER NES "" AND .TYPE:U EQS "A"
 AND .START_TIME = SCHED_TIME1
 AND .START_DATE = SCHED_DATE1 AND .FILLER = SCHEDULED_BY

is syntactically different from

/RSE_RECOG=CAL$CALENDAR.DESCRIPTION WITH
.DESCRIPTON NES "" AND .TYPE:U EQS "A"
AND .START_TIME = SCHED_TIME1
AND .START_DATE = SCHED_DATE1 AND .FILLER = SCHEDULED_BY

Indent those last two lines that begin with "AND" and you may be more
successful.  

Ain't Named Data grand?

K.

Karl,

Assuming spacing is correct (I just can't type...) I think the syntax is the 
same.  I'm still confused on why GOLD S is not working...

thanks,

-jackie

	Jackie,

	Spacing could, indeed, make the difference!  However, you didn't say
which form this is on.  The only form I can find that is close to what you're
describing is TMEVINDEX_FIND...  and *that* one isn't quite what you've shown.
So I'm wondering if they haven't customized their SES a little bit.

	There's no reason this shouldn't work, and work identically.  Could you
be more specific about *which* form, and perhaps even extract the Named Data
*exactly* (i.e., so we're sure there's no typos)?

	Thanks,

	F

    I'm pretty sure Jackie and I have spoken before via a support call
    with SES on this very same form, if my memory serves me correctly.
    This system was most definitely customized so we can rest easy that
    the problem is not coming from SES.  
    
    I did a test with an application I wrote that had similar code in it 
    that Jackie has shown, suspecting that the spacing was the problem as 
    both Karl and Frank mentioned.  I was surprised, however, that even 
    though I took out my spaces, I was shown the correct information in my 
    GOLD S for the SPECIALIST field!  I don't know why though.  Jackie's 
    recognition is quite a bit more elaborate though than mine was.  Here
    is what I did.  Both of my GOLD S's worked.
    
 
;;CUSTOMER;;
    
/RSE_VALID=ASSETS_CR_ENTRY.CUSTOMER WITH .CUSTOMER = CUSTOMER
 AND .SPECIALIST = SPECIALIST
;CLOSE_PRIOR\GET CUSTOMER = OA$SEL_KEY
\GET SPECIALIST = ASSETS_CR_ENTRY.SPECIALIST[CUSTOMER]
/SHOW = ''.CUSTOMER "       " .SPECIALIST''/OPTIONAL/AUTO
    
;;SPECIALIST;;
/RSE_VALID=ASSETS_CR_ENTRY.SPECIALIST WITH
.SPECIALIST = SPECIALIST
AND .CUSTOMER = CUSTOMER
;CLOSE_PRIOR\GET CUSTOMER = OA$SEL_KEY
\GET SPECIALIST = ASSETS_CR_ENTRY.SPECIALIST[CUSTOMER]
/SHOW = ''.SPECIALIST "       " .CUSTOMER''/OPTIONAL/AUTO
 
    
    Just thought I'd share my confusion on why incorrect spacing in my 
    case did not seem to matter or for that matter, give me any errors!
    
    -- Jill

    
    Jill,
    
    I believe that if you have a space at the end of the line in Named
    Data, it will work as well as if you have a space at the start of the
    line.  In other words, I _think_ you have the following spacing:
    (Where I have replaced spaces with underscores)
    
;;SPECIALIST;;
/RSE_VALID=ASSETS_CR_ENTRY.SPECIALIST_WITH_
.SPECIALIST_=_SPECIALIST_
AND_.CUSTOMER_=_CUSTOMER
    
    The biggest problem with this is that it makes the spaces at the end of
    the line _very_ difficult to see.  It also seems like I've seen cases
    where the spaces at the end of a line eventually get lost.  I'm not
    sure if the loss is caused by compiling the forms library, compressing the
    forms library, or what.  Although the leading space may not be
    required, it certainly makes it easier for the myoptic portion of the
    population to see....  ;')
    
    Jack
    

    Perhaps this is just a typo, but the named data posted in .0 seems to
    be missing something:
    
;;DESCRIPTION;;

/PUT=#SEARCH_DESCRIPTION
/RSE_VALID=CAL$CALENDAR.DESCRIPTION WITH .DESCRIPTION = DESCRIPTION /OPTIONAL
/RSE_RECOG=CAL$CALENDAR.DESCRIPTION WITH
.DESCRIPTON NES "" AND .TYPE:U EQS "A"
AND .START_TIME = SCHED_TIME1
AND .START_DATE = SCHED_DATE1 AND .FILLER = SCHEDULED_BY
    
    > AND .DESCRIPTION = DESCRIPTION
    
/SHOW='.START_DATE " " .DESCRIPTION'
    
    This is, of course, what you need it you want the GOLD S to show
    matches for partial entries in any of the fields above this one on the
    form. 
    
    Barb

    Thanks for the feedback Jack!  (Jack was just over here looking at the
    code I was using for my test out of curiosity, unfortunately I had no 
    spaces on either end of the code as Jack had suspected.)  However, I was 
    testing the wrong field on my form for the search. :*)  Boy, do I feel 
    silly.  My named data lists the CUSTOMER field first and the SPECIALIST 
    field second, and the arg form lists them in reverse, so I just tested 
    the second line of the form thinking I was testing the SPECIALIST field 
    and all along I was testing the CUSTOMER field!

    Anyway, when I testing the correct field, the results were that the
    GOLD S does not work and you see ALL information just as Jackie has
    seen.  Therefore Jackie could just be missing a few necessary
    spaces.  Oh, I feel most embarrassed! (blush, blush)

    -- Jill
    

Thanks to all that replied to this.  Barb gets a Gold Star - I needed the 
additional named data on the Description field for this to work.  The spaces
were fine.  

-jackie