I have just double checked the util with the universe in question and the problem was in the universe after all (again, something not picked up by the integrity check process - invalid month/state on a date object).
I have been usin BOXI Universe Documentor V4 with great success. However due to a company policy I had to upgrade my pc to windows 7 with MS Offcie 2010. Now I am getting the error message “Failure in DocumentUniverse() VBO Project - 430: Class does not support Automation or does not suppot expect interface”. Is there a fix for this? Will this program run in MS Excel 2010? I hope so. If it is not possible, is there another way I can document a universe. The BOE that I am connecting to is XI\R2.
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.