7 replies to this topic

[Joseph Bove]

George,

I think we may have a cleaner but somewhat more tedious solution.

We've made our business logic such that if the user , then they can run the search again. We figured that they because they didn't like the results.

Our search windows are 3 LS's.

LS 1 is just a shell

In LS 2, we set a scratch variable like $CAN_CANCEL = 'Y'

In LS 3, if they select a record, we set $CAN_CANCEL = ''

In the exit logic of LS 1

WHILE ($CAN_CANCEL = 'Y')
$CAN_CANCEL = ''
LSCALL(2)
ENDWHILE


hth,

Joseph

[Joseph Bove]

George,

I keep forgetting that the way I document things gets killed because it thinks the way I describe FNKeys is HTML.

We've made our business logic such that if the user press CANCEL, then they can run the search again. We figured that they CANCEL'ED because they didn't like the results.

regards,

Joseph

[andykay]

I have a select window with one input field that will allow me to search for my records.  If I enter the window and that one input field is populated (passed in through the interface), then I want to skip that field and display the records.  If the user then pushes F6 to select, I would like to do exactly that... select the record.  However, if the user pushes F3, I would like to go back up to the input field and let them modify the search parameter.  My window is not a one time.

It seems as though when you skip the only field in an LS, PROIV will treat this field as display only or something.  The reason I say this is because if I put another input field in that LS and don't skip that field, when I push F3 it will stop on my first input field.

What I ended up doing, is putting another input field after the paging part which I would skip if they pushed F6 but stop on if they pushed F3.

George,

You don't need to go through the trouble of adding another field after your paging area. You can do everything (handling the exit and the ability to change your input variable) with 2 logics...for the MOST simplistic operations.

On the Before Field Logic of the input field, before the PS, place logic that

IF INPUT_VARIABLE # '' and @FNKEY # 10 THEN FLD_SKIP

In the EOD/Cancel Logic of the screen place the following:

IF @FNKEY = 10 THEN
ABORT_EXIT()
ENDIF


That's all you have to do. Upon entry, your input variable is not blank and @FNKEY is not 10 so the input screen in bypassed and the Paging Screen finds your input variable records. If the user presses F3, to change selection criteria, the screen attempts to exit but @FNKEY is now 10, so the ABORT_EXIT logic will force a re-entry into the screen. When the cursor gets to the Before Field Logic, it will now stop at the field, allowing modifications, because the FLD_SKIP logic fails to execute. If the user presses F6 to select a record and exit, the ABORT_EXIT logic never executes because @FNKEY is not 10 and the user is allowed to exit out of the screen.

HTH,

AK

[gkwalton]

Thanks for the replys.

I was very interested in both techniques but especially the ABORT_EXIT() technique. I however cannot get this to work. For some reason, when I skip my input field, the EOD/Cancel logic does not get executed when I push F3 or Cancel. If I take the field skip out and I push F3, the cursor will stop on the input field and if I push it again the EOD/Cancel logic will then get executed.

I put a UMSG in the EOD/Cancel logic of the paging screen and that never gets executed.

Any ideas??

George.

[andykay]

George,

The only comments on the CMD from ProIV is: This command is specifically for the EOD/CANCEL Logic of an LS.

I put a UMSG in the EOD/Cancel logic of the paging screen and that never gets executed.

From what you stated, you placed it in the EOD/Cancel section of the PS and not the EOD/Cancel section of the LS.

As a check, place the following UMSG statement in the EOD/Cancel section of the LS and see what is returned...along with the ABORT_EXIT command.

UMSG("@FNKEY = " + conv(@FNKEY),-1)

Check to make sure that when you do press a FN key that the UMSG does return a value.

If the problem was that you had it in the PS instead of the LS, everything should work as it does at the company I am at. Otherwise, I'll need to look at the code to help you out, but there may be some other people here at the RC that might be able to figure out why the command is not working.

Good Luck,

AK

[gkwalton]

Hi AK,

Sorry, I was not clear with my post.

I put the logic in both the EOD/Cancel logic of the PS and the GS. The UMSG was never executed.

George.

[andykay]

The UMSG was never executed.

The only thing that I can think of, without seeing your function's code, is that somewhere a CALLEXIT or FNEXIT is being called. Barring that, you'll have to debug why the EOD/Cancel logic is not being exeucted. Once you do that the ABORT_EXIT command should work.

Good Luck,

AK