Feature Datasets and Relationships are not RDBMS objects which can have access
defined (just rows in SDE-owned tables). The actual tables ("feature classes") can
have GRANTs applied, so the contents of the meta-objects can be restricted to
specific users (if you look inside a FDS as an unprivileged user, it will be empty).
- V
I don't think so. This has been discussed extensively in the past (search forums.esri.com).
It comes down to a design constraint -- If Desktop had to check for the existance of every
table referenced by any FDS before the initial "open" returned data, some sites would be
taking 30+ minute coffee breaks upon initial connect.
Your only options are to either forgo FDS membership (i.e., you're using it as a container,
not to edit related tables with shared topology) or to be less explicit in your FDS naming
scheme.
- V