THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700


S U M M A R Y


DIARY: October 17, 2002 01:39 PM Thursday; Rod Welch

Gary asks about creating SDS records on prior dates.

1...Summary/Objective
2...SAA Operation Failing to Open Records Listed in Reference Field
3...Prior Date Diary Failing to Run
4...Schedule Launch Archive Op Failing 25.Bat
5...Subject Index Shows Progress Will Become Refined Through Experience
6...SDS Update Sent to Gary with Format Corrections to Gary's Records
7...Backup for Daily Interim Changes Added to SDS


..............
Click here to comment!

CONTACTS 
0201 - Dynamic Alternatives
020101 - Mr. Garold L. Johnson
020102 - dynalt@dynalt.com

SUBJECTS
Orientation Editing for Medit and SDS
SAA Open Action Items Listed in Reference Field
Johnson, Gary Opening Files Listed in Reference Field Not Working on
References, open SDS records
SAA Opening Action Items Listed in Reference Field of Schedule Analys
SAA is Broke Not Opening Action Item to Target File and Target Line
SDS Records Zipped and Sent to Rod for Review Found Format Issues tha
Flexible Structure Line Numbers Record Segments
Open SDS record in Ref of SAA and Find Description String in Target R
Citations Create Link SDS to SDS and Editor, macro 985

2512 -    ..
2513 - Summary/Objective
2514 -
251401 - Follow up ref SDS 30 0000, ref SDS 27 0000.
251402 -
251403 -
251404 - This is a test. ref SDS 32 0001
251405 -
251406 -
251407 -
251408 -  ..
2515 -
2516 -
2517 - Progress
2518 -
251801 - SAA Operation Failing to Open Records Listed in Reference Field
251802 -
251803 - Follow up ref SDS 30 DF4N, ref SDS 27 DF4N.
251804 -
251805 - Received an email from Gary transmitting his SDS records.
251806 -
251807 - Gary's record on 0210114 explains this problem is solved. ref SDS 31
251808 - 0001
251809 -
251810 - He found that the corrected record on 020213, ref SDS 30 EL69, was not
251811 - installed with the last update sent also on 020213. ref SDS 30 U1PY
251812 - This may indicate that some work had occurred on the SAA record after
251813 - the date and time of the record that was included in the zip file.
251814 - ..
251815 - In any case, Gary conformed the SAA record to the format
251816 - explained in the record on 020213, and got this problem solved.
251817 -
251818 -
251819 -
251820 -
2519 -

SUBJECTS
Prior Date Diary Failing to Run

260301 -  ..
260302 - Prior Date Diary Failing to Run
260303 -
260304 - Received ... DRT 1 0001 from Gary today explaining a problem...
260305 -
260306 -     Everything appeared to work until I launched SDS again. The new
260307 -     record wasn't moved. The result was that an attempt to edit the
260308 -     record resulted in an error. I copied the record from c: sd 08
260309 -     gljdy 00 (the schedule work directory) to the date directory and
260310 -     changed the name to the appropriate time. I could now access the
260311 -     record from SDS. I made a copy of the record in case SDS overwrote
260312 -     it later, and made some edits to it.
260313 -
260314 - I wrote back asking Gary to zip his records and send them.
260315 -
260316 - Gary's Schedule shows no scheduled tasks nor diary records for today.
260317 - I thought this might be the cause of the problem, but created a new
260318 - task for the date...
260319 -
260320 -                     020701
260321 -
260322 -  ..
260323 - I opened the record, but did not enter a subject nor any text, just
260324 - saved it, closed SDS and started the program.
260325 -
260326 - Gary's Schedule opened and the new task created for 020701 was not
260327 - shown in the Schedule, which is what should occur.
260328 -
260329 - Checked the diary for 020701 and found the new essentially blank
260330 - record just created.
260331 -
260332 - Possible issues...
260333 -
260334 -     1.  It might have occurred that Gary did not enter a prior date to
260335 -         tell the program what date to use for archiveing the new
260336 -         record.  In this case, the current date is still shown, so the
260337 -         Schedule will be unchanged, since the date in the Schedule
260338 -         matches today's date.
260339 -         ..
260340 -     2.  Gary may not have opened the new task he created.  I
260341 -         asked in a reply letter if he converted it to a Diary, but did
260342 -         not ask if he actually opened and save the new record?
260343 -
260344 -         I inclined to thing this may have the cause of the problem
260345 -         today.
260346 -
260347 -         When a new task is identified in the Schedule using either F1
260348 -         or setting a prior date record, there is no actual file in the
260349 -         00 directory until the thing is opened.  On the other hand, if
260350 -         Gary used a record for a prior date to create the new record,
260351 -         that would have avoided the problem, because it starts the
260352 -         user with the file in the 00 directory using the record of the
260353 -         target record.
260354 -
260355 -
260356 -  ..
2604 -
2605 -
2606 - 1406
2607 -
260701 - Called Gary.
260702 -
260703 - We did an exercise to test the prior date diary operation.  It now
260704 - seems to be working.
260705 -
260706 - May have a new problem.  Gary said that, when he launched SDS after
260707 - closing it, the Schedule came up immediately.  He found the new record
260708 - he just completed indicating that the prior date record routine is
260709 - working.
260710 -
260711 -     [On 021106 Gary reports further problems creating a diary for a
260712 -     prior date. ref SDS 34 NZ4G
260713 -
260714 -
260715 -
260716 -
260717 -
2608 -

SUBJECTS
Schedule Launch Archive Operation Failing 25.Bat and 001 Not Assembli
Archiving Diary Records, and SAA

2805 -
280501 -  ..
280502 - Schedule Launch Archive Op Failing 25.Bat
280503 -
280504 - Gary's report that after creating a new record for a prior date, when
280505 - he closed SDS and started the program, the Schedule came up
280506 - immediately, per above, ref SDS 0 8S6J, indicates that the archive
280507 - operation using....
280508 -
280509 -                    c: sd 01 25.bat
280510 -
280511 -
280512 - ...is not running.
280513 -
280514 -     [On 021028 Gary reports that alternate DOS4 has different
280515 -     performance, needs /z to get standard DOS operation. ref SDS 33
280516 -     0001
280517 -
280518 -
2806 -

SUBJECTS
Gary's Subject Index Will Become More Refined over Time

290301 -  ..
290302 - Subject Index Shows Progress Will Become Refined Through Experience
290303 -
290304 - Follow up ref SDS 30 423I.
290305 -
290306 -
290307 -
290308 -
290309 -
290310 -
290311 -
290312 -
290313 -
2904 -

SUBJECTS
SDS Records Modified to Illustrate Format Corrections
Gary's Records Corrected Zip File Updating SDS Code and Work Files Pl
Corrected Records Sent to Gary Illustrating Format for SDS

3306 -
330601 -  ..
330602 - SDS Update Sent to Gary with Format Corrections to Gary's Records
330603 -
330604 - Follow up ref SDS 30 U1PY, ref SDS 24 5Y5H.
330605 -
330606 - Ran an SDS update for Gary using procedures in the record on 021002,
330607 - ref SDS 15 8V3N, as of the last update sent on 021007. ref SDS 24 5Y5H
330608 -
330609 - This includes modified records I received from him today, with
330610 - corrections per above.
330611 -
330612 - Gary can install the update using instructions on 021002. ref SDS 24
330613 - EU7J
330614 -
330615 - Group Manager can be switched using instructions, also, on 021002.
330616 - ref SDS 24 GX9F
330617 -
330618 -
330619 -
330620 -
330621 -
330622 -
3307 -

SUBJECTS
Backup Using Pkzip for Interim Backups Called from File Menu

3404 -
340401 -  ..
340402 - Backup for Daily Interim Changes Added to SDS
340403 -
340404 - Follow up ref SDS 30 425X, ref SDS 29 0001.
340405 -
340406 - Gary might try the new feature created yesterday for interim backups
340407 - of daily work product. ref SDS 29 NR3H  Backup sets are stored on e:
340408 - in....
340409 -
340410 -                 e: backup yymmdd
340411 -
340412 - The location can be changed by editing the batch file....
340413 -
340414 -                 c: sd 01 backup.bat
340415 -
340416 - ...jus change E to any drive of convenience, ref OF 5 JA5I, as shown
340417 - in the record on 021012. ref SDS 29 7A7F
340418 -
340419 -  ..
340420 - Instructions for use simply entail opening the File menu and clicking
340421 - on "Backup." ref SDS 29 E66N
340422 -
340423 -  ..
340424 - A list file is generated to show what has been backed up each pass,
340425 - and selective restore can be accomplished using pkunzip, which is zu
340426 - in the SDS directory....
340427 -
340428 -
340429 -                 c: sd 01 zu.exe
340430 -
340431 -
340432 -
340433 -
340434 -
340435 -
340436 -
340437 -
340438 -
Distribution. . . . See "CONTACTS"