Thanks George, It did show the ^ access code, but I didn't know what I was seeing. I had thought that @ trumped all other codes.
Thanks for your response. Kevin On 1/25/06, George Timson <[EMAIL PROTECTED]> wrote: > Kevin, Field 20.2 was defined so that you were not allowed to edit it. It > gets populated internally by the VistA code. It has a "WRITE ACCESS" of > "^", which was supposed to keep you from getting there. That part worked. > However, the Data Dictionary listing should have told you that fact, and it > didn't. I think that that is a flaw in the DIDH1 routine (PAGE1 ff). I do > not recognize that code; maybe somebody else can remember why the listing is > suppressing this information about READ and WRITE ACCESS. Looks like a bug > to me. > > Thanks, > > --George Timson > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Hardhats-members mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/hardhats-members > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
