Markable Fields

[Mike Palandri]

At 12:51 PM 3/11/98 -0800, you wrote:
>I have a screen where all the fields are "display" only. These are primary
>records with an occurs of 12 records per screen.
>
>I know would like to let the user select one of the records from the
>cluster and then call another screen passing some information from that
>record. I do this by a designer procedure like this:
>
>	PROCEDURE DESIGNER DES1
>	BEGIN
>		PUSH FIELDMARK
>		RUN SCREEN XXXXX PASSING TEMPFIELD
>	END
>
>My problem is I keep getting the infamous "Fieldmark has been disabled
>because there are no markable fields" warning when I compile the screen.
>Consequently it does not do the fieldmarking.
>
>I've tried changing the first field in the cluster to have an id and not be
>display, but still get the warning message when I compile. What EXACTLY
>constitues a "markable field"?


Terry,

SUBK120 is similar to what you describe.  Though it has some TEMP fields
that are used to input search parameters, all the fields in the occuring
primary are DISPLAY.  The user fieldmarks these records to call a dispatch
or an edit screen, (the Edit command on the menu calls another screen, it
does not let them change the marked record.)

It's in PAL$DISK:[PALANDRI.DEVL.SUB.SRC]

(PAL$DISK is $1$DKC206)



Mike