We do not currently use a DA in our environment. A particular division in our department (same notes domain) have a separate address book that is currently cascaded locally for them. They are having issues with name lookups not checking past their local address books once it finds a match. I have enabled Exhaustively check all address books, but it seems to have made no difference. I was considering setting up this secondary address book on the server instead but we really need for nobody else outside of this division to be able to view it and we don’t want the server to do a search of this address book for anybody outside of this group. Can the database be restricted that much via the DA? If so how. Thanks for any assistance.
Subject: Directory Assistance and User Restriction
We setup something similar. Just set the ACL in the secondary NAB so that only those people can get into it. Make sure you give yourself access, and the server. The DA won’t do the lookups in that NAB for a user who doesn’t have access to that NAB.
As for the lookups; try setting “Recipient name type-ahead” to “Local then server” and “Activate recipient name type-ahead” to “On each character”. Also go into Preferences/User Preferences/Basics and enable “allow inline auto-complete in Address bar”.
You might also want to forget the DA and create a Directory Catalog from the secondary NAB on the server that is locked down to set users; then have it replicate only to these users. Set their Preferences – “Local Address books” to be “names.nsf, newdircat.nsf” (newdircat being the dircat you created). Enable replication in the client and you’re all set.