| I believe that's the correct procedure. When the event is created, the
meeting notice is added to MEETING.DAT and all of the attendees are added to
ATTENDEE.DAT on the *creating* node immediately. However, nothing is placed in
either of those two files on any remote node yet.
Now, one of the attendees on the remote node read the meeting request.
There is no entry in the remote MEETING.DAT, so *the first user to read the
meeting request* ends up creating the meeting record. Attendee records are
created, then, only for the users on that node, as they read their notifications.
I'm pretty sure nothing's changed in this area of TM since the original
design.
F
|
| I'm not sure if this is part of the same problem, but I've run into the
following situation when I set up a meeting. The messages go out
without any trouble. When I receive messages from attendees from other
nodes, they appear in my inbox, I read them, but then I get the message
"Error occurred writing to attendee file". This only happens with
messages received back from other nodes.
Is this a bug in ALL-IN-1, or am I doing something wrong?
Thank you,
Kathy Norton
MRO3 Learning Center
|