I'm working in AREV 3.12.

I've got a stockroom multivalue prompt on an inventory window that should have unique stockrooms listed. The same stockroom can't be listed more than once for any given inventory row.

The prompt is set to validate against the stockroom table and make sure that only unique values are entered. I have a post prompt routine call that also checks that there are no duplicate stockroom entries. I have an options call to a popup so a stockroom can be entered into the prompt that way.

My problem is that the popup by-passes both the validation and the post prompt processes. So I (or a user) can type in a stockroom then on the next line of the multivalue prompt use the popup to select the same stockroom and the system allows it. The validation and the post prompt code don't do anything.

I know that the system assumes that if something is selected thru a popup that it doesn't need to be validated.

Is there any way to make sure that the post prompt (at least) gets called so it can check that there aren't duplicate stockroom values within the prompt even if a popup was used to fill in one or more of the values?

Thanks,

Michael Slack

Call the popup from a commuter module and make a manual check.

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

PEBKAC ("Problem Exists Between Keyboard And Chair")

PICNIC ("Problem In Chair Not In Computer")

PIBCAK ("Problem Is Between Chair And Keyboard")

ID-10T error ("Idiot error")

After I don't know how many times I've read the post prompt routine, I discovered that I was missing the right dynamic array angle bracket on the first @RECORD in my count statement.

CNT_STOCKROOMS =COUNT(@RECORD, @VM) + @RECORD # '')

After I put it in, things started to work as expected. I never got any sort of compile error on it.

I was wrong, a selection from a popup doesn't by-pass the post prompt routine call.

I'm amazed at my own stupidity for not seeing that problem earlier.

Thanks,

Michael Slack

ROFL we did wonder. Sort of "Well it works here but…". The

reason it compiles fine is that you now have a boolean comparison :-

Value=(record is less than field number)

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

View this thread on the forum...