Address book priority when having multiple addressbooks

Hi and happy new year to all!

Facing a problem that might have occurred when we switched from cascading address books to directory assistance a while ago. We have 2 address books on the server, names.nsf contains all local users/employees and a second address book containing external contacts. The local address book on each workstation is not involved in this case.

Most users are still on 6.5x of the client. On problem is that with a 6.5.3 client, we see that when typing parts of a name (users first name) and there’s a match in both names.nsf and external addressbook, if I wait for typeahead to resolve (set to ‘on each character’) it resolves to the user from the main address book (names.nsf on server), however if I hit a , (comma) it immediately resolves to the person in the external address book. I have ‘Exhaustively check all address books’ turned ON. If I change this to ‘Stop after first match’, the user from the main address book is resolved.

Is it by design that the external address book is being used as first priority when I hit a comma, or is this a bug? Something wrong with our setup?

Thanks for any responses…

stein