CONTACTS 
0201 - Boeing                                                                                                                                                             O-00000816 0505
020101 - Mr. Garold L. Johnson
020103 - Modeling and Simulation                                                                                                                                          O-00000816 0505

SUBJECTS
Save Contact Record, F2 0705051
Contacts Save Failing in Army M&S Record
Flexible Structure for Contacts Difficult to Manage Consistently Exam
Record Formats Filling Out and Executing Functions
Flexible Structure Line Numbers Record Segments

1307 -
1307 -    ..
1308 - Summary/Objective
1309 -
130901 - Follow up ref SDS 11 0000, ref SDS 8 0000.
130902 -
130903 - Gary made changes to correct the contact record for Nancy, and seemed
130904 - to follow guidance on handling contact records for future work.  We
130905 - reviewed line number formats for creating fields, and the idea to use
130906 - Help in a separate session. ref SDS 0 L74R  He pointed out a
130907 - correction needed to the template for an organization contact record.
130908 - ref SDS 0 LH4I  Developed ideas to create a single set of records for
130909 - contacts without overwriting records created by other users.
130910 - ref SDS 0 E56K Initial solution is to assign separate blocks of
130911 - contact records. ref SDS 0 L64N  Began implementation by sending Gary
130912 - an SDS record update that now includes contact records, and set the
130913 - block of numbers for him to start at 5000. ref SDS 0 HH77
130914 -
130915 -
130916 -
130918 -  ..
1310 -
1311 -
1312 - Discussion
1313 -
131301 - Remedy Fast and Easy to Contact Field and Line Number Errors
131302 -
131303 - Follow up ref SDS 11 T66J.
131304 -
131305 - Gary received the letter last night reported in the record yesterday
131306 - and linked to that record. ref SDS 11 ZS8N
131308 -  ..
131309 - Gary had already done corrections based on guidance in the record
131310 - yesterday. ref SDS 11 KW5I  This indicates that setting the correct
131311 - format is fast and easy using Contact line numbers, also, discussed
131312 - yesterday. ref SDS 11 T66J
131314 -  ..
131315 - We reviewed the changes Gary had made, and everything seemed to be
131316 - formatted correctly.
131317 -
131318 -       After making this review, Gary installed the SDS update sent
131319 -       last night.  He opened the contact for Nancy again, but found
131320 -       the correction was not included.
131322 -        ..
131323 -       Examination of tgj.bat shows that contacts have been omitted in
131324 -       transfers of program updates, in order to avoid overwriting
131325 -       Gary's work. ref OF 1 8K6M
131327 -        ..
131328 -       Today, we changed this approach, per below. ref SDS 0 ZZ6O
131329 -
131330 -
131332 -  ..
131333 - Restoring Line Number Format Restored Address Field
131334 -
131335 - Follow up ref SDS 11 L74R
131336 -
131337 - We examined the design of Contact line numbers.  Gary recognized that
131338 - fields in contact records are set based on indentation of line
131339 - numbers, as shown in Help.
131341 -  ..
131342 - Best practice is to create a record.
131343 -
131344 -     We reviewed the record yesterday suggesting that contact records
131345 -     be formatted based on opening in a separate session that enables
131346 -     viewing simultaneously the template in Help opened with Ctrl F10,
131347 -     and then pressing Enter or double clicking to move to the section
131348 -     that shows a sample template. ref SDS 11 0L3M
131350 -      ..
131351 -     Gary indicated he was not aware that Enter and double clicking can
131352 -     execute links in Help where there is a note saying to Press F1.
131353 -
131354 -
131355 -
131356 -
1314 -

SUBJECTS
Add New Record, Macro 1301

140301 -  ..
140302 - Contact Names of People Do Not Need Comma
140303 -
140304 - Follow up ref SDS 11 LH4I, ref SDS 5 5100.
140305 -
140306 - Gary pointed out that the first name field in the field for listing
140307 - names of people for an organization record has a comma in the
140308 - template, which indicates to a new user that this is a requirement.
140310 -  ..
140311 - We checked Help and noticed that the template record is incorrect.
140312 - While we talked, made this correction.
140313 -
140314 -      h: sd 09 01 021  Individual Contact Record, ref OF 7 0000
140315 -      h: sd 09 01 022  Organization Contact Record, ref OF 8 0000
140316 -
140317 -
140318 -
140319 -
140320 -
1404 -

SUBJECTS
Contacts Common Data Base Maintained Separately
Requirements Objectives
Contacts Data Base Common for Everyone but Managed Separately Using S
Transferring Records
Planning and Concepts
Common Data Base for Everybody but Managed Separately Using Separate
Transfer Files between Computers
Transfer between computers

221001 -  ..
221002 - Managing Common Contacts Separately
221003 -
221004 - Follow up ref SDS 11 LW8K.
221005 -
221006 - We reviewed problem of new records showing up unexpectedly in Contacts
221007 - that raises an issue we have known about, per the situation yesterday.
221008 - ref SDS 11 J06M
221009 -
221010 -      Enable Gary and I and other users to share a common data base
221011 -      without overwriting each others' records.  In this case, I
221012 -      did not overwrite Gary's work, and he has not overwritten
221013 -      anything I have done, simply by luck, I have not created a
221014 -      new record since getting an update from Gary.  Getting each
221015 -      other's SDS records regularly reduces the chances of the
221016 -      problem, but it is only a matter of time before an overwrite
221017 -      occurs, so we need a solution.
221019 -       ..
221020 -      The poorest idea is to notify by email when a new record is
221021 -      created.  Not even sure this would work because the system
221022 -      assigns record numbers, and so it needs a way to avoid
221023 -      different people using the same number for a new record.
221025 -       ..
221026 -      A possible idea is to assign blocks of numbers to different
221027 -      users.  In this case, we have 99,999,999 possible integers,
221028 -      and if we were to include letters, this would increase the
221029 -      number to maybe a billion, depending on how that math works
221030 -      out.  So, within that framework, it should be possible to
221031 -      force each user to create new records within that framework,
221032 -      and they should sort normally to be available to everyone.
221033 -      Of course we run into issues of Medit memory, but we are a
221034 -      long way from that being an issue yet.  For the time being we
221035 -      can assign numbers to Gary say above 5000 to 9,999, then to
221036 -      Jerry from say 10,000 to 14,999, etc.  We can hold preserve
221037 -      these for each user by not overwriting the file that keeps
221038 -      track of the current number for each user, just like we do
221039 -      to avoid overwriting the Group Manager and the letterhead
221040 -      files.
221042 -       ..
221043 -      Not sure if this is an optimum solution, but may be a way to
221044 -      get by while we gain experience to ponder the matter.
221046 -  ..
221047 - Work on 021019 shows the record number index files that need to be
221048 - managed. ref SDS 5 5100   The current values are...
221049 -
221050 -      h: sd 09 02 00000 00  00000822    Orgnz record number inventory
221051 -                                        .... ref OF 4 0000
221053 -       ..
221054 -      h: sd 09 03 00000 00  00000124    Indiv record number inventory
221055 -                            00000127    .... ref OF 5 0000
221056 -
221058 -  ..
221059 - Gary indicated this morning that assigning separate blocks of numbers
221060 - is an adequate solution while the number of users is small.
221062 -  ..
221063 - Changed these index files and sent an update to Gary that now
221064 - includes all of my contact records, so that we are in sync.  Changed
221065 - following two files to start Gary at 5000.
221067 -  ..
221068 - For Gary we can set the following....
221069 -
221070 -      h: sd 09 02 00000 00  00005000    Orgnz record number inventory
221072 -       ..
221073 -      h: sd 09 03 00000 00  00005000    Indiv record number inventory
221075 -  ..
221076 - Modified tgj.bat to now include h: sd 09, and will comment out these
221077 - two index files so they remain unchanged for each user. ref OF 1 6L5N
221079 -  ..
221080 - Gary needs to make the same changes in the batch file he uses to send
221081 - updates to me.
221082 -
221083 -     [...see below showing this was done. ref SDS 0 TH62
221085 -  ..
221086 - Gary should install this update, then do a test to make sure records
221087 - are showing up for him at 5000+.  He can do this by starting to make a
221088 - new organization and also an individual record, then not saving them.
221090 -  ..
221091 - Simply verify that the record number is coming in at 5000.
221092 -
221093 -     [...see below showing this was done. ref SDS 0 TH4O
221094 -
221095 -
221096 -
221098 -  ..
2211 -
2212 -
2213 - 1514
2214 -
221401 - Gary called.
221402 -
221403 - He got the changed records and verified that his records are now
221404 - starting at 5000, per above. ref SDS 0 376W
221406 -  ..
221407 - Gary, also, changed his transfer stuff to me so we do not overwrite
221408 - the record index files, per above. ref SDS 0 EB9F
221409 -
221410 -
221411 -
221412 -
221413 -
221414 -
221415 -
221416 -
221417 -
221418 -
2215 -