I have a large number of AMV's with only a few being visible on a form. In Arev I kept the non-visible value's up with @record. If I understand OI right, you now put the fields on the screen and hide them. But how do you hide a column in an EditTable?

I am not sure I understand why you would ever want to have an "invisible" data table column on a form. Usually you use the invisible feature to hide a record key value which is either a constant or programically added and since by definition a key is single valued, you use an edit line for that. If your "invisible" column is a calculated item it will still be written to the record, so why do you need it to be invisible?

Any way, probably the best way is to stack edit tables on top of one another and then only the top one would be seen.

Another option is to put the "invisible" one on another page of the form and don't provide a vertical Scroll bar. With this approach however, you might still run into it if your table has lots of rows.

You need to hide multi-value data columns in order to update the data "behind the scenes". If the multi-value column is within an associated multi-value group, but for some reason shouldn't be visible, then the simplest way to maintain synchronization is to place the column in an edittable and hide that particular column. That way any edittable row inserts or deletions will affect the hidden data as well.

The way to hide edittable columns is to use the COLSTYLE message using the Send_Message function. Both of these are documented in the Programmer's Reference Guide. There is also some sample code there which can be easily adapted for hiding columns.

[email protected]

SRP Computer Solutions

Don

Thanks a bunch, I used style before but never Colstyle and I never noticed it when I looked through the Manual.

Thanks for the help

K

Don,

I too want to thank you for your response and the diplomatic way in which you by-passed my totally off-base response to Karsten's question.

I also use associated multivalued items with EditTable. Because I have so many of them that are inter-related, I put them on separate pages of the form (so each page has only the proper number of columns to fill up the screen), and use tab templates for the user to move to the different pages on the form. If the user should insert or delete a row on one of these pages that are inter-related to the items on the other pages, will the insertion/deletion be automatically carried through all the pages?

Thanks,

Tom Savell

Hi Tom,

First, your welcome.

Second, can I assume you've been doing this for some time and therefore already know the answer? If not, then my answer would be "no" the inserts/deletes would not be carried through. Especially since OI doesn't track associated relationships at the dictionary level.

My suggestion is to place logic in the INSERTROW and DELETEROW events for all edittables to automatically Send_Message the INSERT or DELETE message to all the other edittables that are connected.

[email protected]

SRP Computer Solutions

View this thread on the forum...