× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. December 2007

Re: hssf setProtection

If you want to prevent the user from changing the file, there are three ideas pop into my mind:

a) Set the "Read Only" Attribute on the IFS object.

CHGATR OBJ('/path/to/myfile.xls') ATR(*READONLY) VALUE(*YES)

-or-

b) Only give the user read permission (not write permission) to the object.

CHGAUT OBJ('/path/to/myfile.xls') USER(whatever) DTAAUT(*R)

c) Serve the file out to the user via HTTP instead of Windows Networking. The user will be able to change the spreadsheet, but won't be able to save it back to the server.


DLee@xxxxxxxx wrote:
Thanks Scott:

That worked perfect, thanks for your help on the boolean.
Unfortunately, I wanted something a user can't undo,(my shortsighted thinking)

I didn't realize I or a user could download the sheet from IFS and undo the protect.

I might end up turning this into a report rather than a excel.

Thanks again.

Darrell Lee
Information Technology
Extension 7127


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.