Hi Fernand, >> You see, I fail to see the overall picture how such a feature would look >> like, could you elaborate? >> > Think on how Spreadsheets are protected. > > DB-doc GUImodifing protection by password > DB-doc-SUBcomponent protection on GUI-USE (simpel: a Table, Query, > Report, Form can been used or not)
Hmm, I think this comparison doesn't work here ... When you password-protect a spreadsheet, then the user cannot open it by any means. Not even by writing a macro to load it. When you would password-protect, say, a query, then what would you expect to happen when the user executes a report which uses the query to fetch the data? Should it also request the password? So, what exactly would you say should be protected for a query? Opening it for data entry? That's easy to prevent from the UI, but 3 lines of Basic code could do it, anyway. Preventing the Basic code approach would be more difficult. Even if you do so - 5 lines of Basic code could retrieve the SQL statement which constitutes the query, and the same 3 lines from before can display this statement. Preventing *reading* the SQL statement which constitutes the query would affect *all* places in Base: Every functionality which directly or (especially) indirectly uses the query (not only in Base - think about mail merging) would need to be prepared for access control - quite a *huge* effort. 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. Ciao Frank -- - Frank Schönheit, Software Engineer frank.schoenh...@sun.com - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
