I have been experiencing some problems implementing Custom LOVs for the first time. The LOV works fine on my PC and my colleague’s, but not on the PC of our friendly user tester. Can anyone help?
WHAT I DID:
- created a custom LOV (the object is a code, and the custom LOV displays both the code and the decode, so the users know what they are selecting)
- checked ‘Export with Universe’
- exported the universe
WHAT THE USER DID:
- created a new report
- dragged the object to the conditions panel
- double-clicked ‘In List’
- double-clicked ‘Show list of values’
- the normal ‘List of Values’ window did not appear (at all) and the user was returned to the Query Panel (no error message displayed)
WHAT I TRIED:
- tested it both my PC and on a colleague’s PC (AOK)
- tried my userid on his PC (failed)
- tested it on all three PCs using my own login, and the user’s login. The LOV failed in all cases on the user’s PC, and was Ok in all cases on my PC and my colleague’s.
- tried different settings of ‘Allow user to edit list of values’ (as recommended in various postings) - no difference
- deleted all the LOV files from the user’s PC, and refreshed the universe
- confirmed that all the LOV files I saved with the universe had been downloaded to the user’s PC
- tried with other objects (about 20!) - none of them work on the user’s PC
- tried a custom LOV WITHOUT changing the selection method (i.e. just saving the list of values, without having a different piece of SQL to generate them). This SEEMED to work, but when I added some custom SQL, it failed again. As we ran out of time, I was unable to double-check this.
- tried Tools/Universes/List of Values… - the ‘Edit’ button failed to display the query panel with the LOV definition (suspicious!), the ‘Display’ button failed to show the LOV window, the ‘Refresh’ button didn’t refresh
- checked the connections - all three have the same connection definition to the same universe and document domains (I’ve seen various references to LOVs being stored in document domains - is there a way I can ‘look’ in the document domain to find the LOVs?)
- pulled hair out!
- consulted BoB - lots of pointers, but couldn’t find anything
- read the manual (there’s a novelty)!
- drafted this posting
ENVIRONMENT:
- BO VERSION: 5.16 full client (all machines)
- USERS: My colleague and I both normally have general supervisor priviledges, but we tried with the user’s userid on both our machines, and could not reproduce the problem
- MACHINES: All similar IBM laptops
- MACHINE ENVIRONMENT: All our users have tied-down desktops, so they cannot (for instance) install their own software etc. This can sometimes mean limitations on what files can be created and where. My colleage & I have unrestricted desktops, and both have administrator privilidges on our PCs. Could this be significant?
- BOMAIN.KEY: I have seen a posting from Dave Rathbun Custom LOV Disappeared indicating there may be problems in using anything except BOMAIN.KEY. All our users (including my colleage and myself) use OHMAIN.KEY. Unfortunately, changing this is not a viable option.
- DATABASE: DB2 v6. This is officially not supported by BusinessObjects, but is Ok most of the time. We once had a problem with document domains (which we do not usually use). Could this be it?
Tony Payne 
(BOB member since 2003-11-21)
(BOB member since 2004-11-03)
(BOB member since 2002-06-17)