| 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 again folks,
Coming to you from Istanbul-Turkey once again and once again I seem to
have a problem with ALL-IN-1/TURKCE V2.4.
This time its the ATTENDEE.DAT file... Here is the scenario:
USERA schedules a meeting with USERB and when USERB replies to
indicating attendance and error message occurs on the screen indicating
it cannot write to ATTENDEE.DAT and no mail is sent back to USERA. The
error message pops up on the screen even before USERB gets to add an
optional comment. That is once 'yes' is entered and USERB decides on
entering a comment or not the error comes up on the screen.
This is what I've checked so far:
Protections: sufficient
location of ATTENDEE.DAT: only one and in .data_share
$ANAL/RMS: no errors
addressing: (users on same system using lastname.firstname format)
data file format: indexed
both users on straight Turkish system
checked ATTENDEE.DAT to see if anything was written: the meetings, the
scheduler and attendee appear but the 'yes' or 'no' don't show up.
I am open to any suggestions!.......
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 219.1 | COuple of things to look at | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Fri Mar 13 1992 12:54 | 13 |
I've not seen this on a US system. Are there any special
characters in the username or full name of the scheduler or the
attendee? What about the ownership of the ATTENDEE.DAT file? Is
it occurring for any other user combinations? Check the
MEETING.DAT file, it's possible that is the cause of the problem.
Error occurred writing to attendee file only happens in two
general circumstances, to the best of my knowledge. The first is
when the file can't actually be accessed. The second is when a
search through the file does not locate the record you were
expecting to update.
Dave Zaniewski
| |||||