11/22/2024 9:51:41 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
Provider security and views
Posted: 12 Jun 08 5:27 PM
|
If I create a view in SQL Server, owned by sysdba, and call it through a provider connection, will it apply security? I thought so, but it's not working as expected.
Can I do this? If so, what are the "rules"?
Thanks,
Jeff
|
|
|
| |
|
Re: Provider security and views
Posted: 16 Jun 08 11:03 AM
|
Phil,
I came up with an answer to my own post. I did it by joining a view column to a table column on a table that will have security applied. Something like this:
Select
Top 50 *
FROM
ACCOUNT acc /* Account TABLE */
INNER JOIN ACCOUNT_ accView on acc.accountid = accView.accountid /* Account VIEW */
Obviously that's just an example - the view in question is a little more complex. But by joining a table with a seccodeid to to a view on the matching key, it a) applies security because of the account table/seccodeid, and, b) doesn't filter results on the join since it's a match. Worked like a charm.
Jeff
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|