Is there a CHANGE event for an AppointmentItem? I have a one-way
interface between Access and Outlook and would like to complete it by
detecting if the AI being changed was created by Access.

The event you're looking for is AppointmentItem.Write.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"David C. Holley" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Is there a CHANGE event for an AppointmentItem? I have a one-way
> interface between Access and Outlook and would like to complete it by
> detecting if the AI being changed was created by Access.

Can I assume that the entire Outlook Object Model is accessible via
VBScript? Just thought I'd ask in advance.

Sue Mosher [MVP-Outlook] wrote:
> The event you're looking for is AppointmentItem.Write.
>

Yes. The details, of course, depend on the type of application you're writing.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"David C. Holley" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Can I assume that the entire Outlook Object Model is accessible via
> VBScript? Just thought I'd ask in advance.
>
> Sue Mosher [MVP-Outlook] wrote:
>> The event you're looking for is AppointmentItem.Write.
>>

I did a cursory investigative study of VBScript (translated I played
around a little). I'm pretty certain that I can code the procedure to
update Access via Outlook, my next question is how would I call the SUB
from VBScript? I'm assuming that the SUB would have to be in VBA to
allow full access to the Access Object Model and all that fun stuff.

Sue Mosher [MVP-Outlook] wrote:
> Yes. The details, of course, depend on the type of application you're writing.
>

Just like Access and other Office applications, Outlook can be automated with VBScript. An event-handler, however, needs to be in a class module, which means VBA, VB, VS.Net, Delphi etc. (An exception is custom Outlook forms, which support Outlook item-level events in VBScript code.)

What's the "big picture" goal of your application?

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"David C. Holley" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
>I did a cursory investigative study of VBScript (translated I played
> around a little). I'm pretty certain that I can code the procedure to
> update Access via Outlook, my next question is how would I call the SUB
> from VBScript? I'm assuming that the SUB would have to be in VBA to
> allow full access to the Access Object Model and all that fun stuff.
>
> Sue Mosher [MVP-Outlook] wrote:
>> Yes. The details, of course, depend on the type of application you're writing.
>>

The BIG, summarized picture is that when a record is added to or
modified in my Access database, Access reaches out to Outlook and
creates an AppointmentItem. The AIs are tagged with the RecordId from
Access which is used to later find the AI. The recordId is stored in a
user defined field. All of the AIs use a custom form which displays the
information in the user defined fields. I would like to code the form to
check the field and then offer an alter that the AI is DB related and
then create the ability to send changes to the AI (Date, Time, etc.)
from Outlook to Access. The code for that aspect I can handle since I'm
quite familar with the Access Object Model. The help that I need deals
with where to place the specific modules and when to call them.

Sue Mosher [MVP-Outlook] wrote:
> Just like Access and other Office applications, Outlook can be automated with VBScript. An event-handler, however, needs to be in a class module, which means VBA, VB, VS.Net, Delphi etc. (An exception is custom Outlook forms, which support Outlook item-level events in VBScript code.)
>
> What's the "big picture" goal of your application?
>

Thanks. That makes it much easier to explain your options. Since you're using a custom appointment form, the logical place to put the code is in that form. Forms use VBScript as their code language.

The event that fires when the item open is ... the Item.Open event. In the form's View Code window, you'll see a Script | Event Handler command that will add the declaration for any item-level event handler. If you want to send changes to the database when the user sames the appointment, you'd use the Item.Write event to run your code.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"David C. Holley" <(E-Mail Removed)> wrote in message news:%2314HV$(E-Mail Removed)...
> The BIG, summarized picture is that when a record is added to or
> modified in my Access database, Access reaches out to Outlook and
> creates an AppointmentItem. The AIs are tagged with the RecordId from
> Access which is used to later find the AI. The recordId is stored in a
> user defined field. All of the AIs use a custom form which displays the
> information in the user defined fields. I would like to code the form to
> check the field and then offer an alter that the AI is DB related and
> then create the ability to send changes to the AI (Date, Time, etc.)
> from Outlook to Access. The code for that aspect I can handle since I'm
> quite familar with the Access Object Model. The help that I need deals
> with where to place the specific modules and when to call them.
>
> Sue Mosher [MVP-Outlook] wrote:
>> Just like Access and other Office applications, Outlook can be automated with VBScript. An event-handler, however, needs to be in a class module, which means VBA, VB, VS.Net, Delphi etc. (An exception is custom Outlook forms, which support Outlook item-level events in VBScript code.)
>>
>> What's the "big picture" goal of your application?
>>

So can VBScript call a VBA Function?


Sue Mosher [MVP-Outlook] wrote:
> Thanks. That makes it much easier to explain your options. Since you're using a custom appointment form, the logical place to put the code is in that form. Forms use VBScript as their code language.
>
> The event that fires when the item open is ... the Item.Open event. In the form's View Code window, you'll see a Script | Event Handler command that will add the declaration for any item-level event handler. If you want to send changes to the database when the user sames the appointment, you'd use the Item.Write event to run your code.
>

I have some proof of concept code in the Item_Close event. The code runs
fine when I'm in design mode for the code using RUN THIS FORM. When
PUBLISH THE FORM AS... and then open the form and close it, nothing
happens. When I design the form, the code is there.

Sue Mosher [MVP-Outlook] wrote:
> Thanks. That makes it much easier to explain your options. Since you're using a custom appointment form, the logical place to put the code is in that form. Forms use VBScript as their code language.
>
> The event that fires when the item open is ... the Item.Open event. In the form's View Code window, you'll see a Script | Event Handler command that will add the declaration for any item-level event handler. If you want to send changes to the database when the user sames the appointment, you'd use the Item.Write event to run your code.
>