WANT the MEDITECH Reports BLOG via EMAIL?

Your email:

About MEDITECH Reports

View John Sharpe's profile on LinkedInI'm your host, John Sharpe, a MEDITECH Report Writing Consultant living in Spokane, WA. Read more ...

Connect ...

Expand your network by connecting on these social media sites:

Sign up for the MEDITECH Reports Blog; details to attend MEDITECH workshops are sent out 1 week in advance to all MEDITECH Report blog subscribers.

These MEDITECH Workshops are sponsored by Donna Carroll at the MEDITECH Community Bulletin

MEDITECH NPR & RW RESOURCES:

Ascii Table: For NPR Report Writer
Loop Builder: For NPR Macros
Key Codes: For CDS Attributes
List Builder: For NPR Macros
MT Report Names: For NPR Reports
MT Structure Viewer: For Physicals
Strings: Format & Sort

HIT Topics

MEDITECH Reports

Current Articles | RSS Feed RSS Feed

Using Kill in NPR

  
 

Question:

I’ve got this line of code in a macro: @Kill(@Root(@med.temp)). Won’t file with that – what can I replace it with, or do I even need it?

Response:

I would look at the object code and you'll see it translates to K(some structure). Instead of doing a kill, do a loop thru the structure if you really want to get rid of it. ""^Q,DO{>:SOME.STRUCTURE[Q]^Q ""^{>:SOME.STRUCTURE[Q]} That's the safe way to do a kill. I use Kill all day long, but it is very dangerous. If you do this K(:STRUCTURE[""]) to kill all records like :STRUCTURE["",SECOND.SUB] that kill would really kill the whole structure, which is very bad in some cases. So its best to just go after the data you really want to get rid of.

Its best not to bypass the syntax checker in the NPR Report Writer; unless its your only option.

Want an alert when the next post is published? Click the phone and Subscribe to the MEDITECH Reports Blog!

Subscribe to the Meditech Blog     

                                                                                                                                                                                                          

Comments

Currently, there are no comments. Be the first to post one!
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics