It really would be easier than having to modify views to include a hidden unid column.
Subject: Solution ? Am I alone in wishing …
So why don’t you use LotusScript.
Set notesDocumentCollection = notesUIWorkspace.PickListCollection( PICKLIST_CUSTOM , [ multipleSelection ] [, server$ ] [, databaseFileName$ ] [, viewName$ ] [, title$ ] [, prompt$ ] [, Singlecategory$ ] )
You get then a notesdocumentcollection and can acess the first UNID with
set docFirst = notesdocumentcollection.getFirstDocument
==> docFirst.UniversalID => UNID
Subject: RE: Solution ? Am I alone in wishing …
Maybe because it isn’t Formula Language, and it would be really nice to use Formula Language if you’re coding in an area that requires Formula Language? that’s just a guess, but I figure it’s pretty close to being on the right track.
Subject: RE: Solution ? Am I alone in wishing …
Or maybe because like so many people, when I get into a groove (read: rut) using one language, I sometimes fail to see the other options available to me.
I use LS all day long for some things, but tend to use formula for client UI stuff (it IS a LOT faster to write than LS for MANY things).
Thanks for the help Marco & Stan.