I have set up a view in an SQL Server 2000 database.
I have then set up a file dsn for SQL Server authentication to the database which Crystal Reports clients can then use to get at the view.
I have granted SELECT on the view and a Crystal Client user can access the view successfully. The problem is that
when the Crystal client expands the Views and Tables below the connection in Crystal Reports, the user also sees three system objects.
They are a table called dtproperties, a view called sysconstraints and a view called syssegments. No permissions have been specifically assigned to the these system objects but the are by default visable to the public role. Why is this?
I've had to specify a:-
DENY SELECT ON sysconstraints TO MyUserRole
DENY SELECT ON syssegments TO MyUserRole
DENY SELECT ON dtproperties TO MyUserRole
to hide them from crystal reports.
Is there something special about these objects I should know?
Dazed and confused
N+, MCDBA 2000, MCAD .NET
I have then set up a file dsn for SQL Server authentication to the database which Crystal Reports clients can then use to get at the view.
I have granted SELECT on the view and a Crystal Client user can access the view successfully. The problem is that
when the Crystal client expands the Views and Tables below the connection in Crystal Reports, the user also sees three system objects.
They are a table called dtproperties, a view called sysconstraints and a view called syssegments. No permissions have been specifically assigned to the these system objects but the are by default visable to the public role. Why is this?
I've had to specify a:-
DENY SELECT ON sysconstraints TO MyUserRole
DENY SELECT ON syssegments TO MyUserRole
DENY SELECT ON dtproperties TO MyUserRole
to hide them from crystal reports.
Is there something special about these objects I should know?
Dazed and confused
N+, MCDBA 2000, MCAD .NET