CONTACTS 

SUBJECTS
SDS v. 3.0
User interface, front
end, 047024

0405 -
0405 -    ..
0406 - Summary/Objective
0407 -
040701 - Follow up
040702 -
040703 - Getting closer to this thing for the first lift.
040705 -  ..
040706 - Completed design of Schedule dos dir structure.  80% complete with
040707 - initialization, 04702.
040709 -  ..
040710 - Changed 04702 solely a processor, and made 047024, the opening menue.
040712 -  ..
040713 - This eliminated the crash that was occurring when User ESC and
040714 - returned to DOS. Apparently, if the profile is the file opened from
040715 - within a batch file, the screen crashes.  I do not remember this
040716 - occurring on other macros like this, but may not have done this
040717 - feature.
040718 -
040719 -
040720 -
0408 -

SUBJECTS
SDS v. 3.0, Initialization
Updating, moving unperformed
to current date in Summary
Archiving Diary Records

0606 -
0607 - 04702
060801 -  ..
060802 - Line 330
060804 -  ..
060805 - Initially I wanted to just rename the old files to the new names, but
060806 - this is not adequate.  Each file has to be opened and its contents
060807 - changed to correlate to the new date, then it should be read back, as
060808 - the new file.  The difficulty with this is that the existing file then
060809 - has to be deleted.
060811 -  ..
060812 - I think the initial idea was to avoid deleting each file.  If the
060813 - files had a common char, like the diary files, we could delete them
060814 - with one instruction.  But these files do not have a common char.
060816 -  ..
060817 - Let's go ahead and rename them.  It happens fast, the files are not
060818 - moved on the disk.
060820 -  ..
060821 - Another idea is that once renamed, when the files are opened, the
060822 - header and date fields can be conformed to the current location on
060823 - the schedule.  This means we just move the positions in the Summary,
060824 - and rename the files, then when they are opened, the contents are
060825 - conformed to their position in the Schedule.
060827 -  ..
060828 - We will not open the files and update their contents for scheduled
060829 - activities during initialization.
060830 -
060832 -  ..
060833 - Pointer processing
060834 -
060835 - The code has to be changed to do the initial stuff once, before it
060836 - processes a single record, because we are now processing one record
060837 - all at once.
060838 -
060839 -
060840 -
060841 -
0609 -

SUBJECTS
SDS v. 3.0, Summary
Format to identify records

0704 -
0705 - Design
070601 -  ..
070602 - Managing Tasks in Schedule Separate from Records on the Disk
070603 -
070604 - It is not clear why creating a new task in the Schedule needs to
070605 - necessarily create an associated SDS record.
070606 -
070607 - We can use a common directory....
070608 -
070609 -        sd 08 00101 00
070610 -
070611 - ...to store files when needed for tasks listed in the Schedule,  The
070612 - Schedule itself can always be stored in this directory as file 00...
070613 -
070614 -        sd 08 00101 00 00
070616 -  ..
070617 - This design enables moving a scheduled task, merely by moving the line
070618 - in the Schedule, file 00, to another date.  When the task is opened
070619 - the record identification on line 1 in the file for the task...
070620 -
070621 -        October 15, 1990 10:30:00
070622 -
070623 - ...and if there is no time assigned to the record....
070624 -
070625 -        October 15, 1990 00:00:00
070627 -  ..
070628 - If the task is scheduled for another date, then when opened the SDS
070629 - record identification would show something like...
070630 -
070631 -        October 23, 1990 00:00:00
070633 -  ..
070634 - This design may simplify updating the Schedule by just move the lines
070635 - representing pending tasks ahead to the next date.  We do not have to
070636 - rename the files on the disk.
070638 -  ..
070639 - So, if there are 10 tasks listed for today, and we only get around to
070640 - working on 3 or 4, then updating the Schedule day-to-day merely
070641 - requires moving lines for unperformed tasks to the next date.  It is
070642 - not necessary to open all unperformed records and modify
070643 - identification, save them to the new date and delete records from
070644 - dates for which no work was done.  Record identification and date/time
070645 - directory sturcture occurs only when and if they are opened.
070646 -
070647 -     [On 901016 use same procedure to enable people to move planned
070648 -     tasks from one date to another. ref SDS 6 LN6N
070650 -      ..
070651 -     [On 040317 background on history of file identification switching
070652 -     between schedule and diary status was reviewed to improve SDS
070653 -     processes. ref SDS 7 PP9U
070654 -
070655 -
070657 -  ..
070658 - What macro enters
070659 - Ref for SDS records?
070660 -
070661 - Need to use this to post follow ups in 04702.
070662 -
070664 -  ..
070665 - Current Archive Diary DB
070666 -
070667 - Made it DS 3 on the temp backup tape.
070668 -
070669 -
0707 -
0708 - 000005 macro 95
0709 -
070902 -  ..
070903 - Fixed this up so it works well now.  The format for identifying
070904 - diary and schedule files for current date is pretty tight.
070905 -
070906 -
070907 -
070908 -
070909 -
070910 -
0710 -