So, the bottom line is: Password protection on a per-object basis either
works for the most novice users only, or is extremely expensive to
implement.
OK : the "maker" of a frontend must decide if a sub-compoment can been
1. "seen" by the GUI (with implement can been run)
2. "altered" by the GUI
the rest of the protection can been done at the Database level
I agree that non-novice users can avoid this protections but at least
we could keep 99% away from our stuff
Greetz
Fernand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org
For additional commands, e-mail: dev-h...@api.openoffice.org
