The code below forces edittable vertical scroll bars to always be visible, it seems not to work in the 32-bit version.

Anyone have any ideas?

Filename=Sysreposwinexes"

Open Filename To Filevar Else Return

Select Filevar

Loop

• Read Next Record Id From Table

Readnext Id Else

Until Do

• Read Record From Table

If Index(Id,'w_Tactic',1) Then

  Read Item From Filevar,Id Then

• Loop Thru All Occurrences Of Search String

    Num_Lines=Fieldcount(Item,@Fm)

    For J=1 To Num_Lines

      Line=Item      

      If Line=Edittable" Then

        Cur_Hex=Line

        If Cur_Hex # "" Then 

• Get Rid Of Leading 0X

          Cur_Hex=Cur_Hex3,9999999

          Cur_Dec=Iconv(Cur_Hex,"Mx")

          New_Dec=Bitor(Cur_Dec,256)

          New_Hex=Oconv(New_Dec,"Mx")

• Put Back 0X

          New_Hex=0X":New_Hex

          Line=New_Hex

• Visim Jrv 1-15-00

• This Is Required If At Somepoint We Need To Turn Off The Oi Edittable Wrapper

• Line=Datatbl"

• End Visim Jrv 1-15-00

          Item=Line

        End  

      End             

    Next J

    Write Item To Filevar, Id Else Null

  End

End

Repeat

]]]Anyone have any ideas?«<

The 32-bit datatable code is different than the 16-bit datatable code. In fact, I had to completely reimplement most of the scroll bar code and did not realize this was a "used" feature.

How important of a feature is this?

Pat

If you have an editable on a form I think looks awful without this.

If I have an editable (all of mine have a unknown and variable number of rows) I leave a gap at the end for the scroll bar. By default this shows as a gap (until it?s needed), this looks nasty. It makes the form look like it was thrown together. You can make the last column resize to fit the space, but that is a cruddy fix if the last column is just single character field (like y/n).

I am surprised more people haven?t complained.

The code I use make all the vertical scroll bars show all the time, this looks in my opinion a lot nicer.

To save you work could I use SendMessage to do this?

Jim,

I suppose we've never complained because we generally choose the best column in the edittable for autosizing. This might be one in the middle or the end…it just depends.

[email protected]

SRP Computer Solutions, Inc.

Jim, I agree with you. It looks awful. So, I committed a whole weekend to handling an edittable sizing the way I thought it should be handled. 154 lines of code. Whew!!! It resizes the edit table for allowances for vertical and horizontal scroll bars (when they are needed). I used SENDMESSAGE, GETSYSTEMMETRICS. After reading the source code and figuring out how the POPUP and POPUP_SUB do it, I got it to work rather nicely.

You also might want to play with colors. Shade every even row gray. It sure is easier to follow the data horizontally.

RESULT=SEND_MESSAGE(FOCUS,'COLOR_BY_POS',COLUMN,ROW,COLOR)

And then you could easily spend weeks and weeks playing with edittables.

What I think is almost a requirement, is having a total row for the edittable. It sure is nice to see totals as they accumulate. For instance, entering a manual check. You use the edittable for the multi value of invoices being paid on the check. And ofcourse you would want to control how much of each invoice amount you want to pay on that check (partial payments). A running total is very nice. Two edittables synched and you are set.

I just thought I would give you some insight on what I do with edittables.

It's going to take me an age to redo all my editables, if I have to pick a column in each one to resize.

View this thread on the Works forum...