fyi - we've encountered some problems with this on NT. If the user is a member of the administrators group then all members of the administrators group are deemed to be owners of the view and have full permissions. VSG just takes the user that you logged in as.
It also appears to change the OS permissions on the privilege file if another user updates a view. This causes most calls to fail. Colin Alfke In sunny - but still chilly - Calgary >-----Original Message----- >From: Amy Cook >Sent: Wednesday, November 24, 2004 8:08 AM > > >Yeah...the frustrating part (for me anyways) is managing the >privileges. >Try on the views, hopefully that will doit. >Or...what we've ended up doing....is generating the schema as a generic >user (we created a unix account called sqlmgr) then when we deliver an >access database, the password is saved. Anyone creating queries will >login via odbc as sqlmgr. > >Just so you know, if you wish to do that now, I believe you'll need to >cleanup the schema then regenerate as the generic user (so everything's >owned by the same person). I'm not sure how you do that in vsg...i >don't have it loaded right now. But...there's probably an option to do >so? ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
