As alternative to using @DBLookup for keywords there should be @GetProfileField("Keywords";NameofKeyword). To get there have an agent (triggered on update, by a view action or schedule) that runs through the documents in the keyword view and creates a profile named "Keywords" and one field per Keyword document. Makes forms soo much faster. Since you use the Profile only as Cache the usual problems with profiles don't apply.