Is there anyway to get around the restriction of keeping your document and universe domain in the same database and still be able to export your .lov files ?
We are still in test, thank God, and decided to separate these two databases because of the potential size and management issues associated with the document domain. Well, now I can’t export my .lov files and I need to export my .lov files with the Universe.
In a message dated 98-06-04 01:17:40 EDT, you write:
Is there anyway to get around the restriction of keeping your document
and universe domain in the same database and still be able to export your .lov files ?
Angela:
What I have ended up with at several different sites is creating two document domains: one is in the same database as the universe domain because of the restriction on LOV files, and the second is in a separate database. The separate domain is where the users are granted access.
In this way you can manage your database sizing with more confidence, as only the universe designers worry about exporting the LOV files, and the users have the ability to do whatever they want in their “own” domain without being concerned about messing up (filling up) a universe domain database.
As far as I know, there is no way to “trick” Business Objects into seeing a document domain in a different database during the universe export process.