I have a shared outlook calendar that contains a modified appointment
item form. The form contains an excel control and a few other controls
along with some vbscript to handle certain functions on the form. The
problem I am having is that this calendar is being used by multiple
users who are updating the excel spreadsheet along with checkboxes and
other controls on the form. The spreadsheet is being saved to a
database along with other info from the form. This works ok when only
one user makes updates to the form, which is the norm. But occasionally
multiple users will be working on the same form, which results in
concurrency problems. What I want to be able to do is prevent items
from being opened by multiple users. Does anyone know if Outlook has
some built in functionality to handle this before I spend time
implementing some sort of locking system?

Thanks,
Sharmil

No, Outlook has no such locking built in. You're on your own.

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


<(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
>I have a shared outlook calendar that contains a modified appointment
> item form. The form contains an excel control and a few other controls
> along with some vbscript to handle certain functions on the form. The
> problem I am having is that this calendar is being used by multiple
> users who are updating the excel spreadsheet along with checkboxes and
> other controls on the form. The spreadsheet is being saved to a
> database along with other info from the form. This works ok when only
> one user makes updates to the form, which is the norm. But occasionally
> multiple users will be working on the same form, which results in
> concurrency problems. What I want to be able to do is prevent items
> from being opened by multiple users. Does anyone know if Outlook has
> some built in functionality to handle this before I spend time
> implementing some sort of locking system?
>
> Thanks,
> Sharmil
>