T
Thomas Kroljic
I have an Access 2000 (SP3) application that uses Automation to create
Appointments in Outlook.
My environment is one server running SBS 2000 with Exchange Server and
another
server (w2k) running in Terminal Services in Application Mode.
I have about 10 - 15 remote users who connect via a DSL VPN connection and
then run the Access application on the Terminal Server.
Within the Access application I use the following code to create the
Outlook Appointment:
Dim outobj As Outlook.Application
Dim outappt As Outlook.AppointmentItem
Set outobj = CreateObject("outlook.application")
Set outappt = outobj.CreateItem(olAppointmentItem)
With outappt
.Start = Me.txtTicklerDate + #9:00:00 AM#
If Form_Contacts.CompanyName > " " And _
Form_Contacts.Institution = True Then
.Subject = Form_Contacts.CompanyName
Else
.Subject = Form_Contacts.LastName & ", " &
Form_Contacts.FirstName
End If
.Body = Me.txtTicklerText
.Location = Form_Contacts.StoreDesc
.ReminderMinutesBeforeStart = 10
.ReminderSet = True
.Save
End With
' Release the Outlook object variable.
Set outobj = Nothing
Set outappt = Nothing
This is working OK except that most users are telling me there is a lag time
of
about 20 minutes before they see the appointment in their local version of
Outlook 2002.
Also, two users recently upgraded to Outlook 2003. They are telling me that
they are
not receiving any new appointments when they create appointments within the
Access application.
While doing some preliminary testing, if the user (outlook 2003 users)
connects to the Terminal Server and they open the Outlook version (2002) on
the TS desktop and then they go into the Access application, it appears to
work, in that if they back out (log off) the terminal server and go into
their local Outlook (2003) and synchronize, the new appointments will show
up.
My question(s): (I'm new to Office Automation. This is my first foray into
this technology)
1. Does the code above work with both Outlook 2002 and Outlook 2003?
2. Should I be aware of or do anything differently with automation in a
Terminal Services environment?
3. Is there normally a lag time before Outlook is updated through office
automation?
4. Do I have to do anything in Exchange to enhance this automation process?
Any help or guidance would be greatly appreciated.
Thank you,
Thomas J. Kroljic
Appointments in Outlook.
My environment is one server running SBS 2000 with Exchange Server and
another
server (w2k) running in Terminal Services in Application Mode.
I have about 10 - 15 remote users who connect via a DSL VPN connection and
then run the Access application on the Terminal Server.
Within the Access application I use the following code to create the
Outlook Appointment:
Dim outobj As Outlook.Application
Dim outappt As Outlook.AppointmentItem
Set outobj = CreateObject("outlook.application")
Set outappt = outobj.CreateItem(olAppointmentItem)
With outappt
.Start = Me.txtTicklerDate + #9:00:00 AM#
If Form_Contacts.CompanyName > " " And _
Form_Contacts.Institution = True Then
.Subject = Form_Contacts.CompanyName
Else
.Subject = Form_Contacts.LastName & ", " &
Form_Contacts.FirstName
End If
.Body = Me.txtTicklerText
.Location = Form_Contacts.StoreDesc
.ReminderMinutesBeforeStart = 10
.ReminderSet = True
.Save
End With
' Release the Outlook object variable.
Set outobj = Nothing
Set outappt = Nothing
This is working OK except that most users are telling me there is a lag time
of
about 20 minutes before they see the appointment in their local version of
Outlook 2002.
Also, two users recently upgraded to Outlook 2003. They are telling me that
they are
not receiving any new appointments when they create appointments within the
Access application.
While doing some preliminary testing, if the user (outlook 2003 users)
connects to the Terminal Server and they open the Outlook version (2002) on
the TS desktop and then they go into the Access application, it appears to
work, in that if they back out (log off) the terminal server and go into
their local Outlook (2003) and synchronize, the new appointments will show
up.
My question(s): (I'm new to Office Automation. This is my first foray into
this technology)
1. Does the code above work with both Outlook 2002 and Outlook 2003?
2. Should I be aware of or do anything differently with automation in a
Terminal Services environment?
3. Is there normally a lag time before Outlook is updated through office
automation?
4. Do I have to do anything in Exchange to enhance this automation process?
Any help or guidance would be greatly appreciated.
Thank you,
Thomas J. Kroljic