This is a sort of catchall of some issues and questions. Among
the installation performance, I just encountered a new problem. I badly need to
transport files from existing FileMan based system to VistA.
This weekend was dedicated to finding how to get KIDS to work – has never
worked. What we found as a cause was a missing Kernel PROTOCOL file. I managed
to export (KIDS) the VistA PROTOCOL file and installed (KIDS) in our existing
FM system. That fixed the KIDS creation problem. Now I think I will be able to
transport existing files to VistA so that I have
those select customized files in the new system.
Another interesting event occurred after loading the
PROTOCOL file. I transported it without data. However, I discovered when we
went live this a.m., a SCREENMAN file I had created in VistA
replaced the SCREENMAN file in my FM system. It was an easy fix, though initially
a bit discomforting. How we came to be missing the PROTOCOL file I have no
idea. I welcome comments explaining what happened.
I also want to make some changes in files I will transport
to VistA, mostly because I think I made some
bad decisions regarding the .01 field, in the original file design. The files I
want to change have a numeric .01 that I would like to change to a pointer to
the PATIENT file. I WANT TO CHANGE THE .01 TO POINT TO PATIENT FILE THEN LOOP
THROUGH THE RECORDS STUFFING THE NAME (field points to patient file),
before I transport the file to VistA. BTW, before such manipulation, the file IS
TRANSFERRED to a new file so the original files remain in their original location
unchanged.
Is this a crazy notion? What kinds of problems shall I likely
to encounter?
Thanks,
thurman
