Guest_imported
New member
- Jan 1, 1970
- 0
Hi,
I've encountered a really annoying problem: Brio, upon opening a BQY, seems to calculate all of the computed columns in every result table... and then execute the document OnStartup script (File -> Document Scripts -> OnStartup)!
Now, if you think about it, this can be quite annoying - especially if you use global variables. In my case, a number of the computed columns use global variables that have to do with the current date. Hence, when I open the bqy, because the global variables have not been define - and Brio automatically starts calculating the computed columns, I get a crap load of "Line (1): glTodayDate is not defined"...
As a workaround, I placed at the end of the document script OnStartup a command to recalculate the result tables, but the console window is still filled with gibberish and can't be cleared automatically, making it hard to debug any other problems later on.
Anyone have any other workarounds around this? One would think that onStartup would be executed first, before anything else is done, but that would be asking too much I guess.
Thanks.
I've encountered a really annoying problem: Brio, upon opening a BQY, seems to calculate all of the computed columns in every result table... and then execute the document OnStartup script (File -> Document Scripts -> OnStartup)!
Now, if you think about it, this can be quite annoying - especially if you use global variables. In my case, a number of the computed columns use global variables that have to do with the current date. Hence, when I open the bqy, because the global variables have not been define - and Brio automatically starts calculating the computed columns, I get a crap load of "Line (1): glTodayDate is not defined"...
As a workaround, I placed at the end of the document script OnStartup a command to recalculate the result tables, but the console window is still filled with gibberish and can't be cleared automatically, making it hard to debug any other problems later on.
Anyone have any other workarounds around this? One would think that onStartup would be executed first, before anything else is done, but that would be asking too much I guess.
Thanks.