Axapta 3.0 form skipping fields

tturney
tturney used Ask the Experts™
on
Hello all,

  I have a form in Axapta 3.0 SP2 that has 8 fields in a column.  Starting at the top field, if I tab or hit enter on the second and fifth fields, it skips over the fields directly below them (3 and 6) and goes to the next fields.  How can I change this to make it go to every field?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
View Solution Only
quale-kaizen

Commented:
goto the form disign and (for each control) set the 'Skip' property to false
tturney

Author

Commented:
Quale-kaizen,

  Thanks for your reply.  All the fields already have the Skip property set to false.  It only seems to be affecting combobox controls.  It doesn't matter if they're connected to a datasource or not.
Commented:
Not sure if this is a bug, it could be.
As a workaround, you can programatically assign tab order to the controls.
void init()
{
    int i, j;
    Array arr;
    ;
    super();
    
    arr = element.tabOrder();
    arr.value(1, 3);  // change the tab order of the 1st control
    arr.value(2, 4);
    element.tabOrder(arr);
}

Open in new window

Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

Learn More!
tturney

Author

Commented:
Quale-kaizen,

  Thanks for your reply and your sample code.  The problem really gets interesting now in that the taborder array is correct.  The combobox fields show as right after the fields above them.  It's just for some reason they skip right past.

Tom T.
quale-kaizen

Commented:
Tom,

This is really strange. I don't think I can reproduce the same behavior.
Can you upload a sample XPO here?

Regards,
QK
tturney

Author

Commented:
Quale-kaizen,

  I went ahead and deleted the form and then re-created it.  I don't know what was wrong the first time, but its fine now.  Thanks for all your help.

Tom T.
quale-kaizen

Commented:
Tom,

I'm glad you solved this.
Sometimes AX caches invalid parts of a given AOD element, which results in strange behavior.
I guess this might have been the case.

Anyway, kudos for the points!

Regards,
QK

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial