Okay, I have this working with scroll bars, which was the biggest limitation of my first version.
So, if you can number the rows before editing and have a known number of rows in the region and don't change the height of those rows while the form is in use, I can give you buttons that are only visible on certain lines, are only enabled on certain lines, or have different captions, colors, or whatever on each line. Basically, the solution is that I place a number of buttons equal to the rows in the scrolling region directly onto the form (not the scrolling region), then position them over the scrolling region so they look like they're part of each row. I give each button a different component ID. Then, I use a stored procedure to figure out what the first row showing in the scrolling region is (using the numbered field) and then SELECT from each row (since I know the first, and the number of rows), examine the data, and then make decisions about how to set each individual button. The effect is pretty startling. Let me know if you want complete instructions on setting it up. It should take you around ten minutes to get it working (once you have the numbering done). -- Larry ________________________________ From: Lawrence Lustig <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thursday, September 15, 2011 10:20 PM Subject: [RBASE-L] - Re: Ideas for buttons in a scrolling region? Okay, I have this (buttons that are enabled on some rows and disabled on others according to some condition) partially solved. Right now I'm looking at ConComp with a scrolling region form on Component where there is a button on each row. Only those components starting with the letter "D" have the button enabled, the others are disabled. My solution so far has a number of limitations: 1. The rows must be numbered and in order -- I added a CompRowNum column to my test table and autonumbered it. (I think I can work around this assuming the rows are ordered and uniquely identifiable even if they're not consecutively numbered). 2. You must know the number of rows in the scrolling region and not resize the scrolling region vertically in the form (wider is okay). I think I could probably work around this. 3. You must suppress the scroll bars on the scrolling region and navigate with by clicking on rows or using F7 and F8 (or other row-by-row scrolling). This is the hardest issue to work around, but I have a glimmer of how to do it. Are any of these reasonable constraints on your problem? If so, I'll try to take it a bit further. -- Larry
