I'm working on an AREV 3.12 application. I'm working on an inventory screen. In an inventory row there is a multivalue stockroom (value mark delimited). For each stockroom there can be multiple Aisle, Shelf, Bin combinations to indicate where in the stockroom the inventory item is physically stored. The Aisle, Shelf, Bin are sub-value marked within a given stockroom. And each is a seperate column.

What I want to do within the screen is once the cursor lands in the stockroom prompt and on a stockroom, then display the associated Aisle, Shelf, Bin information on other prompts. The prompts I'm trying to use are unbound and temporary @record positions and protected. While the cursor is on other prompts, the Aisle, Shelf and Bin prompts are nulled out.

I've tried everything I can think of. With code being called from the perpetual process and/or the prompt's pre-process and/or the post-process. The best I've been able to do is when the cursor moves from the first stockroom to the second stockroom the Aisle, Shelf, Bin information for the first stockroom is displayed. As far as I can figure (and I think I read it somewhere but can't find it again) that the WC_MV% value hasn't been set for the next position value yet at the time of pre or post prompt process.

What I'm trying to imitate is a VB or VB.Net process I've seen where as you go thru the data of one list the associated data for each is displayed in other prompts.

Can anyone point me in the right direction? Or is this something that I can't do without a major coding effort?

Thanks,

Michael Slack

Sounds like an application for a collector window CATALYST call from within the commuter code from the main window. When the user's cursor enters the amv group just show the first sub value in the parent window, and when the choose the row they want, use a softkey SFn to bring up the child collector window with the sub-values 'exploded' into their own amv.

If the user saves the child collector, assign the data back into the @RECORD data fields in the appropriate positions, and only save @RECORD if the user also saves the parent window. Redisplay the window to show them the updates.

It sounds harder than it is, expect for all the repetitive typing required to keep assigning the array and raise/lower them.

I agree with Mr. Johler. Use a collector

Hello:

Thanks for your input.  I thought I might have to go with a collector window but was hoping otherwise.  You told me what I needed to know.

Thanks,

Michael Slack

View this thread on the forum...