<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="http://ideajam.net/ideajam/p/ij.nsf/rsstransform.xslt"?>
<rss version="2.0">
<channel>
	<language>en-us</language>
	<lastBuildDate>Sun, 19 May 2013 07:19:14 +0000</lastBuildDate>
	<title>IdeaJam(tm) : Programmatically prevent document printing</title>
	<description>An RSS feed generated by IdeaJam(tm) for Programmatically prevent document printing</description>
	<link>http://ideajam.net/ideajam/p/ij.nsf</link>
	<image>
	    <title>IdeaJam(tm) : Programmatically prevent document printing</title>
	    <url>http://ideajam.net/ideajam/p/ij.nsf</url>
	    <link>http://ideajam.net/ideajam/p/ij.nsf/LogoSquare.gif?OpenImageResource</link>
	</image>
	<item>
		<pubDate>Mon, 28 Apr 2008 21:05:24 +0000</pubDate>
		<title>Notes Client / Other: Programmatically prevent document printing</title>
		<description>&lt;b&gt;Author:&lt;/b&gt; David Lundy&lt;br&gt;&lt;b&gt;Tags:&lt;/b&gt;  &lt;a href="http://ideajam.net/IdeaJam/P/ij.nsf/ProductByCategory?openview&amp;restricttocategory=print"&gt;print&lt;/a&gt; &lt;br&gt;&lt;b&gt;Idea:&lt;/b&gt; 
&lt;div&gt;There needs to be a way to programmatically prevent a form from being printed.&amp;nbsp; Only allowing users who match a given set of criteria to print would be very useful in a &amp;quot;security&amp;quot; situation.&amp;nbsp; The design checkbox of &amp;quot;disable printing/forwarding/copying&amp;quot; is nice if you like smashing flies with Buicks (read: overkill).&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;A specific example is a database we use to document &amp;quot;incidents&amp;quot; around the hospital.&amp;nbsp; Drug mistakes, employee injuries, patient injuries, etc.&amp;nbsp; Currently, anyone who can see a given incident can print it.&amp;nbsp; There are many times that we need certain people to be able to view an incident report but NOT edit OR print it (it contains sensitive information from a legal standpoint).&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;Another example could be a policies application.&amp;nbsp; One wouldn't want to allow printing of non-approved policies by users other than the creator and/or upper level management individuals.&lt;/div&gt;&lt;br&gt;</description>
		<link>http://ideajam.net/ideajam/p/ij.nsf/0/A814853E2E1842AA86257439006E5BD4?OpenDocument</link>
	</item>
	<item>
		<pubDate>Tue, 29 Apr 2008 05:38:59 +0000</pubDate>
		<title>re: Programmatically prevent document printing</title>
		<description>&lt;b&gt;Author:&lt;/b&gt; Rob Goudvis&lt;br /&gt;&lt;b&gt;Comment:&lt;/b&gt; Even when there is a way to prevent printing, the user can always make a screen dump.So I vote against this idea.&lt;br /&gt;</description>
		<link>http://ideajam.net/ideajam/p/ij.nsf/0/A814853E2E1842AA86257439006E5BD4?opendocument&amp;#commentsanc&amp;id=3676A1A99A3610208625743A00198AFE</link>
	</item>
	<item>
		<pubDate>Tue, 29 Apr 2008 07:51:18 +0000</pubDate>
		<title>re: Programmatically prevent document printing</title>
		<description>&lt;b&gt;Author:&lt;/b&gt; Matt White&lt;br /&gt;&lt;b&gt;Comment:&lt;/b&gt; I'm with Rob here. The illusion of security can actually be worse than nothing at all.&lt;br /&gt;</description>
		<link>http://ideajam.net/ideajam/p/ij.nsf/0/A814853E2E1842AA86257439006E5BD4?opendocument&amp;#commentsanc&amp;id=0D493C725AE4B3008625743A0025A7F6</link>
	</item>
	<item>
		<pubDate>Wed, 30 Apr 2008 21:22:19 +0000</pubDate>
		<title>re: Programmatically prevent document printing</title>
		<description>&lt;b&gt;Author:&lt;/b&gt; Jim Roysdon&lt;br /&gt;&lt;b&gt;Comment:&lt;/b&gt; Sorry, I agree and have had this conversation with many customers. It is impossible to stop someone from "prt-scrn" or screen shotting the data.&lt;br /&gt;</description>
		<link>http://ideajam.net/ideajam/p/ij.nsf/0/A814853E2E1842AA86257439006E5BD4?opendocument&amp;#commentsanc&amp;id=99D0EFCA67E55CDC8625743B006FE842</link>
	</item>
	<item>
		<pubDate>Wed, 30 Apr 2008 22:19:50 +0000</pubDate>
		<title>re: Programmatically prevent document printing</title>
		<description>&lt;b&gt;Author:&lt;/b&gt; David Lundy&lt;br /&gt;&lt;b&gt;Comment:&lt;/b&gt; No worries folks. I absolutely agree with what you're saying. It was requested by one of our users and I thought it was odd that we couldn't do anything but disable printing for EVERYONE (as well as copy/forward).&lt;br /&gt;&lt;br /&gt;Most of our users aren't creative or knowledgeable enough to do screen caps anyhow. ;)&lt;br /&gt;</description>
		<link>http://ideajam.net/ideajam/p/ij.nsf/0/A814853E2E1842AA86257439006E5BD4?opendocument&amp;#commentsanc&amp;id=2726E30BECBEF3428625743B00752C54</link>
	</item>
	<item>
		<pubDate>Fri, 16 May 2008 06:24:10 +0000</pubDate>
		<title>re: Programmatically prevent document printing</title>
		<description>&lt;b&gt;Author:&lt;/b&gt; Charles Robinson&lt;br /&gt;&lt;b&gt;Comment:&lt;/b&gt; You can block Print Screen on Windows. Here is code: { &lt;a href="http://cubert-codepoet.blogspot.com/2008/05/sntt-disable-print-screen-key-win32-api.html" rel="nofollow" target="_blank"&gt;Link&lt;/a&gt; }&lt;br /&gt;</description>
		<link>http://ideajam.net/ideajam/p/ij.nsf/0/A814853E2E1842AA86257439006E5BD4?opendocument&amp;#commentsanc&amp;id=5DF303EB9A44BD598625744B001DADFF</link>
	</item>
	<item>
		<pubDate>Fri, 23 May 2008 13:34:00 +0000</pubDate>
		<title>re: Programmatically prevent document printing</title>
		<description>&lt;b&gt;Author:&lt;/b&gt; Phil Petts&lt;br /&gt;&lt;b&gt;Comment:&lt;/b&gt; David, &lt;br /&gt; &lt;br /&gt;Whilst I agree with everyone else about the print-screen problem (although Charles has a solution for that above), you can control who can print the document by having a computed $KeepPrivate field on the form. You set the field to "1" if you don't want the user to print / forward etc. I've done this in the past and it works, I think by default it was set to "1" then I added a button to print, which clears the field, prints the doc, then adds the "1" back in. &lt;br /&gt; &lt;br /&gt; Another approach would be to have two copies of the form, one with the disable printing/forwarding/copying set, one without (use a subform to store all the fields etc). Then use a form formula in the view(s) to calculate which form is used by which user. &lt;br /&gt; &lt;br /&gt; HTH &lt;br /&gt; &lt;br /&gt;Phil.&lt;br /&gt;</description>
		<link>http://ideajam.net/ideajam/p/ij.nsf/0/A814853E2E1842AA86257439006E5BD4?opendocument&amp;#commentsanc&amp;id=303F83D8A5CE879C8625745200450810</link>
	</item>
</channel></rss>
