Richard: Am I accurate in thinking Pick __USED__ to have file level security but it doesn't exist in the U2 products because, it was always said, the O/S takes care of security (aka: "we don't need no stinkin file level security")! Perhaps, having dbms security isn't such a bad idea after all. :-)
Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Taylor Sent: Friday, May 27, 2005 8:09 AM To: [email protected] Subject: RE: [U2] Uniobjects hack [snipped] 2) Convert the account to an SQL schema. You can then attach file level security via the SQL user. Just remember to create a security entry for Public too otherwise you could end up locking out all the other users that are not subject to the tighter security. (i.e. GRANT ALL TO PUBLIC) If you are trying to allow them to access a file, but control what they do you may be out of luck. However you could use triggers to a least create audits. [snipped] Rich Taylor | Senior Programmer/Analyst| VERTIS 250 W. Pratt Street | Baltimore, MD 21201 P 410.361.8688 | F 410.528.0319 [EMAIL PROTECTED] | http://www.vertisinc.com ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
