如何区分“names.nsf”中不同用户的联系人列表 Domino 服务器？
我正在从 Domino 服务器访问所有用户的联系人。 但是所有用户的联系人都保存在单个文件（“names.nsf”）中，我想以用户方式显示它。
谁能告诉我如何区分不同用户的联系人列表？
I am accessing contacts of all user's from Domino server.
But contacts of all user's are saved on single file ("names.nsf") and i want to display it user wise.
Can anybody tell me how to differentiate contact list of different user's?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
服务器上的names.nsf应该是您的公司地址簿。 个人用户不应具有写入此文件的权限。
每个用户的本地安装上还应该有一个名称.nsf。 如果他们是漫游用户，则可能会在其漫游用户配置文件下将其复制到服务器。 这是您在服务器上看到它的唯一一次。 但它不会覆盖服务器的名称.nsf，也不会以任何其他方式与服务器的名称进行交互。 他们有不同的replicaID。 该数据库有一个字段“
如果用户在断开连接的情况下可以复制服务器的names.nsf，但应该使用不同的文件名或在不同的文件夹中进行设置，以便它不会覆盖他们的个人names.nsf。同样，它将具有不同的replicaID，因此它不会与它们的个人名称交互。
这两个数据库也具有不同的设计模板。
还可以通过目录协助设置一个或多个共享地址簿。类型的地址簿可以在内部定制开发，并且通常由一群人使用，例如，采购部门可能有供应商联系人的地址簿，我能想到的区分他们的唯一方法是。 $UpdatedBy，除非创建此数据库的开发人员添加了一个字段来记录条目所有者。
names.nsf on the server should be your corporate address book. Individual users should not have access to write to this file.
Each user should also have a names.nsf on their local install. If they are a roaming user, this might be copied up to the server under their roaming user profile. That is the only time you'd see it on the server. But it doesn't overwrite, or in any other way interact with, the server's names.nsf. They have different replicaIDs. This database has a field "
Users can replicate the server's names.nsf down if they work disconnected, but it should be set up with a different filename, or in a different folder, so that it doesn't overwrite their personal names.nsf. Again, it will have a different replicaID, so it won't interact with their personal names.nsf.
The two databases have different design templates as well.
It is also possible to set up one or more shared address books via Directory Assistance. These types of address books can be custom developed in-house, and are often used by groups of people. For instance, a purchasing department might have an address book of the vendor contacts. The only way I can think of to tell them apart would be $UpdatedBy, unless the dev who created this database added a field to record the entry owner.