| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hello, Time Management on 2.4 + 3.0 Customer's heavy TM users have a problem with conflicts and editing thereof. Basically the situation is that say user A creates a meeting inviting user B for 10 am 4-Jun-1992. Then later on user A schedules some recurring events inviting several users including user B. However one of these recurring events is the same date + time as the first meeting above. User B has already read the first invite and said Yes I will attend. However he now gets the second invite and due to their working practises he accepts that as well ie says Yes to attending. Then at a later date he will decide which he will be attending. He then decides that the first invite is the one he will attend and so goes to TM EV to select the second event to change that to notify the scheduler that he will not be attending. This however is not possible a Sel will give the 2 records but only the first can be selected and an Index while showing the second instance will not actually allow you to edit it, it will always edit the first instance. Anybody got any workarounds as this is causing them severe grief, as they use TM a lot and schedule a lot of conflicts to be resolved later. I guess work-around is unlikely as it seems to be the calendar reply function working behind the scenes that is prob - meeting.dat does not have duplicate keys and so that is not the problem especially as the scheduler does not have the same problem. cheers Alan I have tried this in v3 and it is still the same - but I wondered if anyone had hacked this for themselves.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 819.1 | There's hope | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Fri Jun 05 1992 15:28 | 8 |
Hi Alan,
The MEETING.DAT does not have duplicate keys, but more than one
entry in the personal calendar may have the same value for the
.MEETING_POINTER field. This problem is currently being
investigated by engineering.
Dave Zaniewski
| |||||
| 819.2 | Sorry for tardy gratitude..... | WAYOUT::CROOKS | Things that make you go Hmmmmm.... | Mon Jun 15 1992 11:24 | 8 |
Thanks for the info Dave, Did you report this recently...? The SPR will still be going through - a patch would be very useful....(any TM developer like to comment) cheers Alan. | |||||
| 819.3 | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Tue Jun 30 1992 14:22 | 6 | |
The original problem reports are not recent. A large number of
customers insisting upon a fix is. Comments about a possible
resolution, I'll leave for engineering.
Dave Zaniewski
(just back from holiday)
| |||||