Thanks Terry and Arnaud.
Lennox.

Terry Ford <[EMAIL PROTECTED]> wrote: 
On Apr 16, 2007, at 6:47 AM, Lennox Jacob wrote:

> Terry Ford  wrote:
> One thing is to encode the files to make them difficult for the
> average user to read and another to make them difficult to find
> outside of your program.
>
>
> If the user can easily find them and try to
> open them in a text reader then they can also be damaged or otherwise
> rendered unusable.


Lennox wrote:

> Can they be rendered unusable if they were not saved?

Not saving will have no effect on the file as you have only read them  
to your program. That wasn't the point of my statements anyway.

> Apart from locking these files, (or making them read-only), are  
> there any other way of "protecting" them when they are opened by  
> other programs?
>
> Is it possible to open the files as copies? And would that  
> circumvent making the original rendered unusable?

The point I was trying to make was that the files should not be in  
such an obvious location that the user would find them easily. Such a  
place might be a folder inside your application's containing folder.  
This makes it easier to see them in the "Finder" and can be opened  
outside of your application.

If these files are invisible or otherwise rendered un-viewable to the  
finder then the average user will not notice them. Another option is  
to place them in an ApplicationData (support) folder. There are easy  
ways to make these files accessible to your program but not to the  
"Finder" and I honestly think that is all you really need.

Terry



_______________________________________________
Unsubscribe or switch delivery mode:


Search the archives:



       
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to