Hi,
Depending on your OS, you can set the security at the file ( or directory) level and allow read only permission to everyone and other rights to specified users.
Once a report is created it is just another file to the file system
Note that even if you restrict the rpt file to ReadOnly, a user can export it to another rpt file without this restriction.
Also, if what you have in mind is protecting report designs as intellectual property, a ReadOnly approach doesn't serve that purpose. There are other solutions for that situation...
Cheers,
- Ido
CUT, Visual CUT, and DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.
Hi Ido- thanks for the info -- any recommendations as to protecting reports from modification. I am trying to centralize rptg, and keep end users from altering reports, thereby 'breaking' them.
Ido-- The folder permissions will work for my objective, however,I wanted to know (since I cannot find any supporting info) whether there are options within an individual Crystal Report that allows permissions on that report to be set(in versions 8 or 8.5)--(?)
My DataLink Viewer allows you to generate an encrypted rpz file from an rpt file. You keep the rpt file and your users get the rpz file. Your users can run the rpz file in DataLink Viewer, just like they can any rpt file. However, they can't open the rpz file in Crystal to see/change the design of the report. They also can't export it to an rpt from DataLink Viewer (this ensures full protection). Of course, you keep the rpt file for yourself.
hth,
- Ido
CUT, Visual CUT, and DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.