Virtual Table populated by another VT behaviour

[jmartyr]

Hi all,

I have one VT (call it vt1) which is populated with an sql statement referring to another VT (call it vt2). When I'm building my app and I click on vt1 in the table menu (for instance to drag it to a grid), the app builder will crash unless I've loaded vt2 somehow. Simply clicking on vt2 in the table menu does the job, for example, and I can go about building my app.

If I do manage to create a grid populated by vt1, Lianja crashes when I start the app.

I'm not sure if this is intended behaviour for Lianja or not. If it is, where can I load vt2 so that it will always be loaded before vt1 attempts to reference it? vt2 is not directly used in my app, so I'm thinking something along the lines of loading it in the init delegate for the section that calls vt1?

[barrymavin]

Please submit a ticket with an example of how to reproduce this.