One of the beauties of the xcard paradigm is that is so stinking flexible. You aren't tied to a lot of the vagaries of many other RAD's.
So I can only tell you how I solve this problem in the applications that I work on. I have a substack for settings/preferences/security (sometimes they are all together, and sometimes they are separated into separate stacks). Obviously you can also use custom properties if you choose. I like the stack solution because it's easier to develop the interface. It also makes it easy to have recursive or combination group privileges and access. But that's just my solution. In more traditional databases, you...never mind. xcard is much more elegant. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
