Creating Appointments via Access on Terminal Server

[Thomas Kroljic]

I have a client with the following environment:

1. Dell PowerEdge server (JMserver) running SBS 2000 (with Exchange Server)

2. Dell PowerEdge server (TermServer) running w2k in Terminal Server
Application mode

I have an access database on the Termserver server. This application is used
by 10 - 15 remote users (they access the server via a DSL VPN connection.)

Within the access database application I just added the following code to
add appointments to their OUTLOOK calendar:

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 appears to be working but there appears to be a lag time before their
Outlook Calendar is updated, is this normal? The users use the OUtlook that
is located on their local desktop, not the one located on the Terminal
server desktop. Will this cause any problems? The user will normally make a
connection to the JMserver (SBS 2000) via a VPN connection and then
synchronize their outlook application.

Will running the above code within an Access application on the terminal
server work properly in my clients environment since all the remote users
are using their local Outlook and synchronizing with the Exchange Server?
Should I be using a different method?

In testing it appears to work even though there is a lag time of 30 seconds
to 2 minutes. Am I using the right method/approach?

Thank you,
Thomas J. Kroljic

 

[Sue Mosher [MVP-Outlook]]

Think about it: If the user is synchronizing, they won't see the updated
information in their local copy until a sync occurs after the data is
changed in the mailbox itself.