Since the tables are created at runtime the generated-code of those tables doesn't get generated until you run the designer generation process, so you won't be able to access those tables from the llbl api until then. So, I can think of a few solutions, like for example you could run the command-line-generator from you code, and later compile it as an specific library containing those classes and load it dynamically, all this from your handled code. Somehow this seems very laborious to me. Unless you really need what I mention before, an easier approach would be send the table parameters (name, filter, fields...) to an stored procedure and call this from the llbl api.