Columns not scrolled in a form

berniebernie Member Posts: 7
edited 2006-07-21 in Navision Financials
Hi,

I am working on a form which shows an overview of all the projects they have.

This form contains so many fields that it can be scrolled with the scroll bar.

Our customer wants that the first two columns of this form, that contain the projectnumber and description, will not be scrolled, so that they allways can see these columns.

According to the helpdesk of Navision Holland the solution for this problem is to use a matrix-form. But I do not know how to get more than one textbox on the "right" side of this form. Neither does Navision Holland.

Has anyone else a solution for this problem?


Bernie

Comments

  • jpjp Member Posts: 47
    You could make the MatrixSourceTable the Integer table, then create an array of field names to display as the column headers, and another array of values to display in the matrix cells.

    -jp
    -jp
  • John_TegelaarJohn_Tegelaar Member Posts: 159
    Don't think the MatrixBox is the right control for this. The horizontal direction (the columns) can have only a single reference and you need successive fields from you projects table.

    But it tickles the mind when such a "you can't do that" comes along...

    Why not, just for the fun, think out loud of how to create a fixed column nevertheless...

    I would think of making an array of textboxes to mimic the fixed column(s), next to a normal tablebox. In the OnFormat trigger of (all) the fields in the table box you put a call a function that fills the textboxes with the projectnames. On opening the form, the OnFormat trigger is fired for each -first to last- visible row, so that's usable to fill the textboxes the first time. When the user starts vertical scrolling, things are becoming a bit complicated. Now it's to find out if it was a single line or a "page" up/down... Hmm, would mean some checks on which textbox corresponds with the lines shown. Scroll one line up means that the first table line is new, scroll one line down means the last one. Scroll a page down means that the previous last one table line is now the first. Should be possible to detect the logic flow in this, and update the textboxes accordingly.

    Would mean you have to give up resizing the form, but that's the price to pay.

    Comments? Alternatives? Anybody? <img border="0" title="" alt="" src="images/smiles/icon_smile.gif" />

    John
  • lstroemlstroem Member Posts: 18
    I think this can be solved much easier.

    Forget about "locking" columns. Instead create 2 textboxes outside the TableBox which contain the values that the user wants to see permanently.

    This solution is also consistent with the rest of Navision Financials - it is implemented in, for example, Form 39 where 2 textboxes show the Account Name and Balancing Account Name.

    /Lars

    BTW: The "lock column" feature was standard in Navision Classic (version 3.xx)
    Lars Strøm Valsted
    Head of Project & Analysis, Navision Competence Center
    Columbus IT Partner
  • Michael_SchumacherMichael_Schumacher Member Posts: 81
    Hello there,
    I'm sorry for warming up this very old thread, but I found nothing else regarding locking columns in Tableboxes. :cry:

    I tried it already with 2 tableboxes, everything looks fine as long as there are less records than visible lines in the boxes.
    As soon as there are more lines scrolling of the boxes is not coherent.

    The solution with two extra textboxes above the tablebox is not suitable because there is already a big header and this would take away 2 more visible lines.

    When you are editing a Job Budget you have to see as much lines as possible....

    Has anyone got another solution for this?

    Does anybody know why the lock column feature has been taken out?

    Will it be available again in future versions?

    I know, questions after questions, but my boss is always asking me about this..... [-o<

    btw: we are using Nav 4.01 DE
    regards,
    Michael Schumacher

    oh, what day is it? Backup day. OK, let's dump all data to /dev/nul ;-)
Sign In or Register to comment.