CONTACTS 

SUBJECTS
Schedule Changed Method of Developing New Task Filenames Macro 95 in
Planning New Task Filenames Macro 95 in Schedule Based on List in 00
Planning Schedule Changed Method of Developing New Task Filenames Ma
Schedule Maintenance Needs to be Automatic to Avoid Accumulating Pre
Schedule Task Numbers being Renumbered from 0001 Causing a Big Mess
F1 Shift F1 Make New Task 004 Failing When Current Diary from Schedu
New Task in Schedule Using Current Diary Record Failing

1109 -
1109 -    ..
1110 - Summary/Objective
1111 -
111101 - Follow up ref SDS 4 0000, ref SDS 3 0000.
111102 -
111103 - Gary reported more of the problems encountered a few weeks ago.
111104 - Review of his files showed some issues caused by defective code, that
111105 - has since been corrected.  After clearing problems caused by defective
111106 - code, SDS worked correctly on Gary's Schedule 00 file and directory.
111107 - ref SDS 0 6Q5W  Submitted updated code to Gary.  Called and worked on
111108 - removing the errors in the Schedule 00 file and the 00 directory.  He
111109 - then ran the updated code and the result was successful. ref SDS 0
111110 - J168
111111 -
111112 -
111113 -
111114 -
111116 -  ..
1112 -
1113 -
1114 - Problem
1115 -
111501 - Received a letter from Gary this morning with extracts of his SDS
111502 - Schedule 00 file showing that problems reported initially on 040330
111503 - where a filename for a new task is being created incorrectly by using
111504 - letters. ref SDS 3 7O9U
111506 -  ..
111507 - Gary called later, and after discussion he sent his SDS records for
111508 - review and correction.
111510 -  ..
111511 - Problems found...
111512 -
111513 -    1.  00 Scheduel File....
111514 -
111515 -        a.  There are two files with the filename...
111516 -
111517 -                     0001
111519 -             ..
111520 -            This may have occurred from trying to use file 1108 with
111521 -            the name...
111522 -
111523 -                  SDS - Learning -- Subject Global Pointer Mechanism
111524 -
111525 -            ...to create a new task in the Schedule, since there are
111526 -            two files with the same description, and one of them has
111527 -            duplicated the filename 0001.
111529 -             ..
111530 -        b.  Schedule Analysis and Adjustments (SAA) content has been
111531 -            replaced by the content of file 1108 for...
111532 -
111533 -                  SDS - Learning -- Subject Global Pointer Mechanism
111535 -             ..
111536 -            As a result, SAA content has to be replaced from a backup
111537 -            on Gary's computer.
111539 -             ..
111540 -            Deleted the 0001 file from the disk.
111541 -
111542 -                [...below, Gary replaced this file. ref SDS 0 6H56
111544 -             ..
111545 -        c.  Filename "SDS" somehow got created and has a blank task
111546 -            desription.
111548 -             ..
111549 -            Removed this from the 00 file.
111550 -
111552 -         ..
111553 -    2.  00 Scheduel Directory....
111554 -
111555 -        a.  File 0000 is a mistake, because SDS is not designed to
111556 -            create a file named "0000."  It has the content of 1108,
111557 -            indicating that Gary used the record 1108 as a template to
111558 -            create the new task, and things fell apart.
111560 -             ..
111561 -            Since this is a clear mistake, deleted this file.
111562 -
111564 -             ..
111565 -        b.  00_GOOD.ZIP
111566 -
111567 -            This file is not an actual SDS schedule file.  Gary created
111568 -            it the other day when we started to mobalize, and were
111569 -            having problems.  It saves the 00 directory, but is no
111570 -            longer needed.
111572 -             ..
111573 -            This file might be the cause of the getting a file with the
111574 -            name 0000, and then getting a duplicate of 0001, because of
111575 -            improvements to solve similar kinds of problems, reported
111576 -            on 040317. ref SDS 2 056N
111578 -             ..
111579 -            For time being to test the theory, will not delete this
111580 -            00_... file, and will open Gary's Schedule and try to use
111581 -            F1 to create a new task, and see what happens.  F1 is the
111582 -            code that is called when a new task is created using F1
111583 -            Shift F1 that led to problems Gary reports this morning,
111584 -            per above, ref SDS 0 YY6G,
111585 -
111586 -
111588 -  ..
111589 - Testing Replicate Failures - Failed, Indicates Problem May Be Solved
111590 -
111591 - Just tried F1 in the Schedule, with the extraneous file, 00_....zip,
111592 - in the 00 directory, ref SDS 0 O76U.
111594 -  ..
111595 - Did not get a failure.
111597 -  ..
111598 - The program created the next filename 1121, which is correct.  This
111599 - result suggests that the current code will accomodate leaving an
111600 - extraneous filename in the 00 directory, however, generally this is
111601 - not "best practice."
111603 -  ..
111604 - Tried opening the file 1108, which Gary created today for...
111605 -
111606 -                  SDS - Learning -- Subject Global Pointer Mechanism
111607 -
111608 - ...per above, ref SDS 0 6P9G, and then calling the functions F1 Shift
111609 - F1 (which can also be executed from the "Manage" menu), and this
111610 - created another entry in the Schedule...
111611 -
111612 -                  SDS - Learning -- Subject Global Pointer Mechanism
111613 -
111614 - ...which is normal; when a new task is create it initially has the
111615 - name of source file.  This new task has a filename of 1121, which is
111616 - correct.  There is a master Follow up link below Summary/Objective
111617 - that opens the source file, 1108, which is correct.
111619 -  ..
111620 - This functioning suggests that perhaps changes the past few days,
111621 - since Gary received updated code has fixed the prior problem.
111623 -  ..
111624 - Gary may be doing something that is not obvious.  Since we cannot
111625 - replicate the problem, there is no assurance the problem is fixed.
111626 -
111627 -
111629 -  ..
1117 -
1118 -
1119 - 1126
1120 -
112001 - Called Gary.
112002 -
112003 - Reported results.  Decided to update SDS code on Gary's office
112004 - computer.
112006 -  ..
112007 - Prepared transfer from 040301.
112009 -  ..
112010 - Uploaded transfer to the web.
112012 -  ..
112013 - Gary downloaded onto his computer and installed.
112015 -  ..
112016 - While the file transfers were occurring, Gary changed the files on his
112017 - computer for his SDS records to reflect changes made above.
112018 - ref SDS 0 H95I
112020 -  ..
112021 - He restored the 0001 file from a back up to have his action items
112022 - current in the SAA record, per above. ref SDS 0 5R4S
112024 -  ..
112025 - After installing the updated code, Gary opened the Schedule, and then
112026 - ran the op that failed earlier, per above. ref SDS 0 5R8T
112028 -  ..
112029 - The results of using F1 Shift F1 with the updated code were
112030 - successful.
112031 -
112032 -
112033 -
112034 -
112035 -
112036 -
112037 -
112038 -
112039 -
112040 -
112041 -
112042 -
1121 -