context is everything 
Well, it's not on the Internet (!) and it does everything you specified with minimal, efficient code. To any User, it's simply 80 (or more) buttons.
Since, in fact, you are building a reservation system for a number of club members, you are going to need an online system to manage them.
I
'm already doing it. I entered all the hours in a listview and selecting I make a reservation.
But now I was thinking of a simpler interface: this is why I thought of putting all the hours of a day in a single screen.
But it gives me an error on when any Button.click.
Maybe because I also have other buttons? For example, exiting the screen
After selecting the button I have to read a record on the db, show it in another screen, modify data and then, if everything is ok, save it. This is why I find it more convenient to use the buttons and not the html page.[quote="ChrisWard, post:22, topic:22321, full:true"]
Well, it's not on the Internet (!) and it does everything you specified with minimal, efficient code. To any User, it's simply 80 (or more) buttons.
Since, in fact, you are building a reservation system for a number of club members, you are going to need an online system to manage them.
[/quote]
No, there is only one.
Setting the Background Color and the Enabled of the button can be done directly against the given component.
The index in list and select item by index blocks cancel each other out, and cause trouble for you if global buttons is incomplete.
Component blocks make very poor messages. They are dripping with component guts. Maybe use the button.Text as a message?
what about clicking on that error to find out more?
Taifun
Trying to push the limits! Snippets, Tutorials and Extensions from Pura Vida Apps by 
Taifun.
That would be the same with the HTML 
It just avoids having a huge amount of Arrangements and Components.
Please export your project and post it here.