| 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 | 
    
    ALL-IN-1 3.0
    
    A customer has just called with a time management problem, where
    meetings have suddenly appeared in users accounts.
    
    Everything was okay until Monday, when perople logged in, and ALL-IN-1
    told them that they've got some meetings waiting. (I understand that
    that means that the message has been read, but not replied to.)
    
    If they try to use AM to answer the meeting, it brings up the details
    of a meeting which they have already replied to (most of the time, the
    meeting is in the past!), and when they attempt to reply to it again.
    they get a message about the attendee record not being found.
    
    I know thnat the number of outstanding meetings comes from the symbol
    OA$MEETING_COUNT_DISPLAY, but where does this symbol come from?
    
    Thanx
    
    Steve.
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 3288.1 | briefly | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Thu Sep 16 1993 17:41 | 16 | 
|         This symbol is set during the ALL-IN-1 initialization sequence,
        sometime before OAINI.SCP is accessed.  (I've played with this
        recently)  For each event notice, in the user's .A1CAL file, dated
        today or later, a check is made in ATTENDEE.DAT to see if a
        non-blank response has been recorded.  For every blank response,
        the counter is incremented by 1.
        
        If AM finds something to respond to, the count is probably
        correct.  The most likely cause for unanswered meeting requests
        for a lot of users, is somebody restoring ATTENDEE.DAT from
        backup.  Other possible causes are usually related to problems
        accessing ATTENDEE.DAT (now or in the past).
        
        Hope this helps.
        
        Dave Zaniewski
 | |||||