# @entsel

Description:

Tells an "Input Processing Table" what to do after record is displayed, but just before the prompts are displayed and the cursor is placed at the "Enter Selection" prompt.

This processing does NOT lock the current record. This means you can not write to real fields within an @entsel routine.

A common use for @entsel is to combine it with the -d flag of clerk. This flag tells filePro to clear the standard prompts off the bottom of the record screens. This allows you to put up custom prompts of your own. Using @entsel will put these custom prompts up at the appropriate times.

For example: The following command line and code will display a custom set of prompts. It would be up to you to make sure there are appropriate @keys for each of the displayed prompts. Just changing the prompts will not stop filePro from intercepting the keys it normally does like (H)ardcopy, (B)rowse, (U)pdate and so forth. They will still be active unless you build @keyH, @keyB @keyU processing of your own. Any combination of filePro (factory installed @keys) and custom @keys of your own is acceptable, just remember that yours will override the factory supplied @keys.

rclerk filename -s1 -d

@entsel If:
Then: show "\r P \r-Print, \r U \r-Update, \r M \r-Modify, \r X \r-Exit"
Then: end

IMPORTANT: Remember that @entsel processing does NOT lock the record on multi-user systems, so you can not make assignments to real fields within the @entsel code. In other words, a real field can not be the left side of an equals statement.

Note: @entsel trigger is used only on INPUT processing table.