Larry: Wow, I am clueless how you could get that to work when use a scrolling region or even f8/f7 to move through the scrolling region! How can you possibly know which numbered row is the top one?? I doubt the users ever resize the form. I could probably add a column to the table that could be dynamically numbered starting with #1. What would happen if within the form the user wants to delete or add rows (both of which I allow)?
Karen In a message dated 9/15/2011 9:53:42 PM Central Daylight Time, [email protected] writes: > 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 > > > >
