LabVIEW
cannot edit table control
That's because you're continuously updating the table's properties.
That causes the input to reset...
If you want two tables with one scrollbar, you need a separate scrollbar. You can't catch events for table scrollbars, but you can catch the external scrollbar's event.
Search LabVIEW like a graph! 
Your table loses input focus 20 times per second due to your hammering of property nodes. Properties only need to be written if the new values are different from the old ones. If the properties never change the never need to be written once set.
First of all, I recommend not to use tables as user inputs, especially for numerics because everything is treated as strings and things are not validated.
If you need a table where some fields can be entered by the users, make the entire table a control, but discard edit operations that would modify the fixed entries. No need for all that song and dance! Now the entire thing can be scrolled at once at any time. You can even make the user fields a different background color (e.g. white vs. light gray).
Can you take a step back and describe exactly what you want to do (not how you want to do it!). What does the user see? How does the user interact? What should happen if the user enters something? What does the user typically enter (numbers, names, etc.)? How big does the table get? How often do the programmatic entries change? How many columns?
@paul_cardinale wrote:
Maybe this.
You also have to turn off selection scrolling. If not, the user can move the table cells by selecting cells outside what's visible.
Also, you can move the scrollbar, and while you have the scrollbar captured, leave the table. You won't get an event...
The only proper solution is to make an external scrollbar. And turn off selection scrolling.
This is all way to hard in LabVIEW. For starters, we need a load more events.
