G
Guest
My company's intranet guru is giving me grief about connecting to my
database. I am planning to secure the database with user-level security,
which is the source of her grief. Can I simply set up a read only user for
the intranet connection and tell her what the the logon and password are? I
don't know anything about ASP, but surely the logon and password can be
hard-coded into the web page. She wants administrative privileges to the
database for herself, which I don't believe is necessary (there are already
four people my boss wants to have admin privileges, which is too many IMHO).
She is also insisting on moving the database from its current shared drive
folder location to another server that I do not have access to, for
"security" purposes. Is this really necessary if the database has user-level
security?
database. I am planning to secure the database with user-level security,
which is the source of her grief. Can I simply set up a read only user for
the intranet connection and tell her what the the logon and password are? I
don't know anything about ASP, but surely the logon and password can be
hard-coded into the web page. She wants administrative privileges to the
database for herself, which I don't believe is necessary (there are already
four people my boss wants to have admin privileges, which is too many IMHO).
She is also insisting on moving the database from its current shared drive
folder location to another server that I do not have access to, for
"security" purposes. Is this really necessary if the database has user-level
security?