Click here to Skip to main content
14,982,136 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
is it possible to hide or disable the right click context menu from the ActiveX controll of Adobe Acrobat reader. i am using this controll on windows form to display some records and i dont want the user to take print or save the document. i have disabled the toolbar using arguments but i didnt find one for context menu.

can anyone suggest me a solution?? if any other controll available for this senerio, thats also fine with me ??

thanks
Posted

I suggest you reconsider either your approach or your mindset. Trying to disallow the user to utilize something he can see on his screen is doomed to fail. Haven't you too already circumvented some website mechanics trying to hinder you from saving an image? Even if you somehow succeed in disabling the context menu, you won't be able to hinder the user from taking a screenshot. It will negatively impact the user experience with your application and they will look for alternatives. And if the data of your records is that sensitive, why show it in the first place?
   
Comments
   
Agree, a 5.
I would also remind that the whole idea to assume that the users can use Adobe Acrobat reader plug-in or any other PDF reader is wrong. PDF is not a part of W3 standards and is purely optional.
—SA
[no name] 16-Mar-15 0:40am
   
Thank you!
vikaskallidantheyil 16-Mar-15 0:39am
   
i have a requirement that i should show the documents to the users so that they can refer it but not to save or print it...
[no name] 16-Mar-15 0:41am
   
Show my answer to whoever gave you that requirement, maybe he/she will reconsider.
   
I usually comment harder on such references to "requirements": why should we waste time on the inquirers who do not make decisions on the subject of the question? Why asking the experts then? Ask the person who gave you the "requirements". Isn't it logical?

The problem is more serious in real life. One of the most difficult obligations of the developers getting requirements is to review, falsify them, and turn some of them back for fixing of the problems found. In practice, even if the requirements were wrong, and then implemented, with bad results because of bad requirements, the big part of responsibility is put on the people who implemented them. It may seem unfair, but in fact it makes certain sense: for the developer implementing something using requirements, it's easier to see the problems. Developers are actually expected to turn questionable requirements back.

In all cases, using "requirements" as an argument in discussion with an expert is totally incorrect. The expert's role is different.

—SA
[no name] 16-Mar-15 1:26am
   
Good point. I'll tell the next "candidate" exactly that. The thought (or "logic" if you will) actually isn't completely new to me but since I only ever gave myself requirements for the last 16 years my field of view became a bit narrow I guess ;-)
- Sebastian
   
:-)
   
In addition to the discussion on "requirements", I can add one thing.

What would you say if one of the requirements would be delivering some messages faster than the speed of life? There are laws of nature, right? Likewise, there are laws of human society, albeit depending on culture and historical period. Laws of technologies (except those dictated by the laws of nature) are just part of them. What they "required", even if it was possible, would be considered as the violation of the very basic customer's rights. Depending on the setting, in presence the of competition, such attempt could even through your project out of market in no time...

—SA
[no name] 16-Mar-15 1:40am
   
Agree. Though it could be that this is some in-house solution where they don't have to care about competition. Still they will fail hindering their employees finding creative ways to make their life easier ;-)
   
Sure. This is just the example of possible consequences.
—SA
Solved by setting Edit and print password settings to the pdf file itself...
https://www.wpi.edu/Academics/ATC/Collaboratory/HowTo/AcrobatX/printing.html[^]
   
v2

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)




CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900