I do something similiar using Execute SQL (much simpler) and a table with all button labels). Adding a button, however needs manual copy paste (except I would include placeholders)....I will take a look at your solution. Learnt so much from you over the last two decades!!!
One thing you should always consider with using ExecuteSQL is that if there is an open record on the client, then the performance can degrade significantly. It's always suggested to use a Commit Records just prior to any ExecuteSQL call. Plus, for some, they don't like having to learn SQL. But, I love using it myself. You can also use AI now to compose your SQL statements for you!
I do something similiar using Execute SQL (much simpler) and a table with all button labels). Adding a button, however needs manual copy paste (except I would include placeholders)....I will take a look at your solution. Learnt so much from you over the last two decades!!!
One thing you should always consider with using ExecuteSQL is that if there is an open record on the client, then the performance can degrade significantly. It's always suggested to use a Commit Records just prior to any ExecuteSQL call. Plus, for some, they don't like having to learn SQL. But, I love using it myself. You can also use AI now to compose your SQL statements for you!
35:37 Why are you concerned about character length? Is it because of having to transfer data from and to the cloud where the solution is hosted??