I have two sets of AMVs on the second page of a multi page form. Each AMV is similar - first column is CODE, second is DESCRIPTION (which is a symbolic column). When entering rows into the first AMV group, the cursor moves from top to bottom, scrolling automatically until the bottom row is reached, and then continues scrolling up - normal behaviour. The second AMV group behaves differently: the cursor remains on the top row and does not move down - the entries are scrolled immediately, and are therefore hidden to the user unless he scrolls up to see them. If I remove the AMV grouping between CODE and DESCRIPTION it then works fine.

Can anyone explain this?

If CODE in both AMV groups is the same dictionary item, WINDOWS will do this. Create a second dictionary descriptor that references the same FMC with a different name and bind that to the prompt:

CODE (FMC=5) DESCRIPTION(SYMBOLIC) AMVG=1

CODE_A (FMC=5) DESCRIPTION(SYMBOLIC) AMVG=2

Thanks, Warren

The AMVGs reference different dictionary columns. So I am still stuck!

I suggest you check how the two fields are grouped. I have had no problem scrolling up to ten fields, however none were symbolic.

Mark

Is the AMV depth properly stated for the 2nd group? Is the group number properly stated (in the groupings screen?) Are the code field numbers properly stated in the template?

Yes, Yes and Yes. If I duplicate the workings on a SINGLE page form, it all works OK. There could be something wrong or damaged in the window source code. It's a monster window, and will take time to recreate, but I may just try that.

Thanks.

Which version of ARev? 3.12 does funny stuff now and then with AMVs especially if you have hidden labels in the screen.

Hi Warren

I think the client is still on 3.1. Maybe I'll run an upgrade and see if anything changes. Thanks for the tip.

Nick

The problem exists in 3.12, I'm not sure about 3.1 or 3.11 (Aaron could probably answer this one as 3.12 is pretty much his baby).

Can you reproduce the problem if you paint a minimum screen that that has a similar setup (i.e. at least 2 pages, with 2 or more AMVs on 2nd page)?

If you cannot reproduce the problem then I'd suspect the 'hidden label bug'. Check the include record LCPOSITIONS as to where the hidden label flag is located and check the prompt layouts in the WINDOWS record. Be sure to back it up. Aaron posted the source of a utility that clears this flag, but I don't remember what keywords to search on. You'll have to modify the program because is goes through the whole WINDOWS file as is.

Here's the source code Warren mentioned.

Personally, I think it's something in the symbolic. Are they the same? Is the code small? I'd bet it's doing something with an AMV common var.

akaplan@sprezzatura.com

Sprezzatura Group

View this thread on the forum...