There is no such built-in security. You'd have to build your own scheme into the code behind the form. For example, you can check Application.Session.CurrentUser and, based on the result, call Item.GetInspector.ShowFormPage to show a particular page.

Signature
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
> When designing a outlook form, is there a way to hide certain tabs from
> certain users? Or is there another way to do this? I am new to designing in
> outlook so any help is greatly appreciated.
>
> Thanks.
HappyOne - 16 May 2008 17:46 GMT
Thanks for your fast reply. I have one more question. The
Application.Session.CurrentUser only returns the current user. Is there a way
to find out which group this user is in? Thanks in advance.
> There is no such built-in security. You'd have to build your own scheme into the code behind the form. For example, you can check Application.Session.CurrentUser and, based on the result, call Item.GetInspector.ShowFormPage to show a particular page.
>
[quoted text clipped - 3 lines]
> >
> > Thanks.
Sue Mosher [MVP-Outlook] - 16 May 2008 18:19 GMT
"group" as in membership in Active Directory security or distribution groups? If you're limited to the Outlook object model, you'd have to look at the membership of each group. Outlook doesn't expose group membership as part of an AddressEntry. In Redemption, however, you get an RDOAddressEntry.IsMemberOfDL property.

Signature
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
> Thanks for your fast reply. I have one more question. The
> Application.Session.CurrentUser only returns the current user. Is there a way
[quoted text clipped - 7 lines]
>> >
>> > Thanks.
HappyOne - 16 May 2008 21:26 GMT
What would be your suggestion in filtering out what users can and cannot see?
Would the best be multiple forms in different folders and set the rights on
those shared folders?
> "group" as in membership in Active Directory security or distribution groups? If you're limited to the Outlook object model, you'd have to look at the membership of each group. Outlook doesn't expose group membership as part of an AddressEntry. In Redemption, however, you get an RDOAddressEntry.IsMemberOfDL property.
>
[quoted text clipped - 9 lines]
> >> >
> >> > Thanks.
Sue Mosher [MVP-Outlook] - 16 May 2008 22:05 GMT
Remember that forms are just UI/code templates. It is the items in the folders that contain the data. Blocking someone from using a custom form doesn't prevent them from seeing the data in the folder. It's impossible to say more without details on what you're trying to hide.

Signature
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
> What would be your suggestion in filtering out what users can and cannot see?
> Would the best be multiple forms in different folders and set the rights on
> those shared folders?
>
>> "group" as in membership in Active Directory security or distribution groups? If you're limited to the Outlook object model, you'd have to look at the membership of each group. Outlook doesn't expose group membership as part of an AddressEntry. In Redemption, however, you get an RDOAddressEntry.IsMemberOfDL property.
>> > Thanks for your fast reply. I have one more question. The
>> > Application.Session.CurrentUser only returns the current user. Is there a way
[quoted text clipped - 7 lines]
>> >> >
>> >> > Thanks.