 Home |
 Content |
| Purchase |
| Ready-to-use samples |
| Online resources |
| Forum |
| Links |
| Happy readers |
Anonymous
using ACLLookupAccess . . . (by Dallas Gimpel, 05/25/2005 12:50:14 PM) |  |
ACLLookupAccess returns 0 for the access level when I pass it a pointer to a NAMES_LIST structure built by NSFBuildNamesList. It doesn't crash or raise an error - just doesn't seem to work (at least not the way I want it to). This was the result regardless of whether I built the structure using the full canonical form of my name, valid wildcard entries, or groups to which I belong.
Based on the description in the documentation (http://www-12.lotus.com/ldd/doc/tools/c/6.5/api65ref.nsf/ef2467c10609eaa8852561cc0067a76f/4a07efddf9e31578852567110054a3a4?OpenDocument) and my own observations, it seems as though NSFBuildNamesList determines group membership by way of the private NAB as opposed to using the Public NAB or even a union of the two. This is one of the behaviors I specificly wanted to avoid to begin with. But even so, I really don't see where the problem is since, at least in this case, I happen to be explicitly defined in the ACL of the database in question (which, also happens to reside on a server). It seems like there should be a reliable way to programatically determine a user's *real* access to a given database regardless of where it's being accessed. Am I missing something?
thanks,
dgg