Base Macro - Click on Table Row to Open Record

edit

Note: Ignore comment in code about storing variable in Global. Mistakenly left in from copied code. No globals used in macro.

This looks like exactly what I need. Awesome to see it working. I figured it was possible somehow. Thank you sir. Now to inspect the code and figure out how it's done. It's a good way for me to learn a few things.

There's one weakness to this approach. Strangely, a macro attached to a table control's click event triggers no matter where the click occurs, even on scrollbars, nav buttons at bottom, etc. If there are more records than can display, you can't scroll down without clicking to trigger a record edit launch. Too bad the developers didn't think of that and only trigger inside the cells. I think I'll not worry about it and tell users to use mouse scroll wheel instead of clicking on scrollbars.

One goofy way to get around this click problem is to attach the macro to the table's "when losing focus" event instead. Then it requires a click anywhere outside the table control. While that might seem strange, a "load" or "open" button (with no event) adjacent to the table might tempt a click and feel like a sensible user experience. Don't know why click events attached to table columns don't work. They literally do nothing.

No need for 'goofy' approaches. Just add oEvent ( Sub GetID(oEvent) ) and you can check for conditions. Assign to middle button, or left button with a modifier ( such as + Ctrl or Alt key) or even right button although this is mostly for context menus. You need more knowledge on using events and MRI to examine properties and methods.

See -> struct MouseEvent

and -> constants group MouseButton

and -> struct InputEvent

So with oEvent present, then:

If oEvent.Buttons <> 4 Then exit sub

at the beginning of the routine will only execute the routine if the middle button was pressed.

Also, click events in columns do work. What is probably confusing is the method in which they work. If you click in a table control field, it selects the field. They next click in that field activates the mouse click event. Now I can't say this is the way it should work but only that is the current process.

In my case, the column clicks don't work at all, no matter how many times I click - 1, 2...30. If I attach the same Subroutine to the table control mouse click event, works every time. Even if I write a Sub that has only msgbox "Hello" and call it on column event mouse click... nothing. That's why I chose the table control click event instead. Your attached file also has table control click event, so I figured you encountered a similar problem. Otherwise column click makes far more sense.

Strange. I can get the column click event to work by switching it from the table control on YOUR file... but not in mine. Even if I write an entirely new subroutine, it won't trigger it on a column click. Can't think of any other explanation than a very obscure bug I'm encountering. Like you said, it takes two clicks on your file. But in mine, it just doesn't work. I'll just tolerate the table control click for now since it works.

Since I couldn't ever get the events attached to columns to work, I ended up making a separate "Edit" button that triggered the event instead. Works great and is probably more "expected" behavior than clicking inside the table control anyway.