The .UNV files should be usable in the same way that 3.1 and earlier versions were. The .UNX files created by the IDT will not be exposed in the same way.
can you please explain: why is it neccessary to execute the SELECT statement for every object (lov) in the universe? I cannot see any benefit from this (except creating lots of traffic on the database).
Hi lucky
I didn’t realise that it actually executed the query.
I am currently working solely with unix files so am not in a position to look at this for a while.
But by all means you can have a play with the vb yourself.
Cheers
Sandi
It’s not a choice. I have seen the same behavior. When touching certain aspects of the LOV definition via the SDK, the query executes. I don’t know why, and there’s no way to turn it off.
I ran into the same issue Dave describes a long time ago. As a workaround, I changed the connection (locally only) to one that points to a non-existent server. The select statement still executes, but errors out immediately and the LOV information can be accessed as normal. Definitely annoying.
I am trying to run this against a UNV in BI 4.0 SP4 with no luck. I get the error message “Can’t find project or library”. It seems to be on the library designer. I don’t even get to the point of supplying what system I am looking at. Could it be my version of VB or Excel?
Any reason why the Instances should now be giving me a macro error? It used to work … i find it really very useful, and although it isnt critical, would be nice to have if anyone knows what i need to do???