A
anovak
I think I've found the answer the theory for allowing all PMs to run a
macro that connects directly to SQL and reads certain tables to build
dialog boxes for the user interface.
I've created a separate database on the server called UNTS_Tools and I
have created several views that reference back to views in the
ProjectServer_Reporting database.
My thinking is that all I have to do now is use the views in this
database within the macro and grant everyone (or at least all Project
Server - and perhaps Portfolio Server - users) read only access to
this new database.
I've brought up the Database Properties dialog box for the database
via SQL Mgt Studio, but I have to idea whether to add the [guest]
user, [public] role, etc. nor which explicit permissions to grant
(connect only, connect and select, etc.)
If someone has been down this road a bit, I would appreciate any
specific instructions you could provide to put this last permission
piece in place.
Thanks!
Andy Novak
UNT
macro that connects directly to SQL and reads certain tables to build
dialog boxes for the user interface.
I've created a separate database on the server called UNTS_Tools and I
have created several views that reference back to views in the
ProjectServer_Reporting database.
My thinking is that all I have to do now is use the views in this
database within the macro and grant everyone (or at least all Project
Server - and perhaps Portfolio Server - users) read only access to
this new database.
I've brought up the Database Properties dialog box for the database
via SQL Mgt Studio, but I have to idea whether to add the [guest]
user, [public] role, etc. nor which explicit permissions to grant
(connect only, connect and select, etc.)
If someone has been down this road a bit, I would appreciate any
specific instructions you could provide to put this last permission
piece in place.
Thanks!
Andy Novak
UNT