usually every application has at least one configuration document which contains some information about our application and of course you should to use these data in your application.
1. @DbLookUp and @DbColumn every timefirst way is to create a view where you can find this document (@DBLookUp or @DbColumn)and receive needed data each time when you want, but it's very slowly way and stupid, because there are a lot of dblookup will be.
2. transmit Id of config docthere is one another way which I prefer to use is to transmit the id of conifg documents (using @dblookup or other ways) and then each time when you need some data, you can use @getdocfield(id; fldName)
3. collect all data in 1 field in profile and then use this fieldAnother one good approach is to save all data in configuration document in one field, for example [fldName1]fldValue1:[fldName2]fldValue2:[fldName3]fldValue3 and so on, after that you can load this field using just 1 @dblookup and then parse it and receive this data. This method I used very often too, but now I switch to method #2.
ok, i know that we can you real profile documents, but i don't like to do it, and I'm not able to tell you why is it so :)
but any suggestion and new idea will be appreciate !