No, you can't early bind to get intellisense on that.
What I usually do myself is set up public properties and methods in the
designer that end up exposed to the property page. Then if a configuration
in the property page is changed I can call the method in the addin to update
things. I can read and set the public properties as needed to get/send
information with the addin.
BTW, if you need reference to the Outlook.Application object in your
property page code make sure to declare it this way to get a copy of the
trusted object from your addin:
Implements Outlook.PropertyPage
Dim objSite As Outlook.PropertyPageSite
' In the UserControl_InitProperties procedure:
Set objSite = Parent
Set golApp = objSite.Application 'golApp is global Outlook object for PP
--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm
"RobL" <(E-Mail Removed)> wrote in message
news:98596560-071E-49E9-BD70-(E-Mail Removed)...
> Hi Ken,
>
> thanks for the advice.
>
> I'm now up and running. One more follow-up question is:
>
> When, in the Property Page, I have the line:
>
> Set myObj = Application.COMAddIns.Item("MyOfficeAddin.Connect").Object
>
> as per the Microsoft KB page you sent me, is there a way I can dim myObj
> to
> give me intellisense access to the public variables in
> MyOfficeAddIn.Connect?