The "proper" way to edit the SIGNATURE BLOCK PRINTED NAME field 20.2 is to
use the option Electronic Signature code Edit under the User's Toolbox menu.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Holloway,
Thomas (EDS)
Sent: Wednesday, January 25, 2006 7:55 AM
To: [email protected]
Subject: RE: [Hardhats-members] Re: Why can't I edit field 20.2 in file
#200?

Kevin,
   I think this has come up before.  The field is locked with the
internal, programmer lock method which is node 9 in the DD entry.  e.g.
^DD(200,20.2,9)
   If you kill that node, temporarily of course, you can edit the field
with FileMan.  The usual caveat applies:  any time you bypass security
controls, without knowing the precise reasons for those controls, you
place your database integrity at risk.  

Thom H.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Toppenberg
Sent: Wednesday, January 25, 2006 6:53 AM
To: Hardhats Sourceforge
Subject: [Hardhats-members] Re: Why can't I edit field 20.2 in file
#200?

 I have a nurse practitioner in my site that I entered into the system
 incorrectly.  Instead of JANE DOE, FNP, I should have entered her as
 JANE DOE, GNP.

 No problem I thought, I'll just edit that.  Specifically, I needed her
 name at the bottom of signed documents to have the correct initials.
 This name is stored in field 20.2 in file 200.

 But I can't seem to edit this field in fileman!  Here is a screen log
(trimmed)


 INPUT TO WHAT FILE: NEW PERSON//
 EDIT WHICH FIELD: ALL// 20.2??  <-------------- notice that it
pretends there is no such field.
 EDIT WHICH FIELD: ALL// 20.3  SIGNATURE BLOCK TITLE
 THEN EDIT FIELD:


 My DUZ(0)="@", by the way.

 So I thought that there must be some restriction in the data
 dictionary.  So I examine the field with VPE, but I can't see why I
 can't edit the field.

 (I had the output from VPE here, but it triggered a spam filter, so
had to remove it)


 I ended up changing the initials by directly editing the global, which
 I shouldn't have to do.  I used the VPE global editor, and after I had
 made the change, was given a warning that I might be deleting a global
 (though no option to cancel was provided).

 So I have made the change successfully, but I don't feel that I did it
 the correct way.

 Any thoughts?

 Kevin


-------------------------------------------------------
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=k&kid3432&bid#0486&dat1642
_______________________________________________
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=k&kid3432&bid#0486&dat1642
_______________________________________________
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

Reply via email to