Excuse me for Jumping In (I forgot the little acroynym) you could:

1. Have a Backup
2. Create the File itself
3. Rename it to something conspicuous and do a SET RESOURCE (or something like that)

Personally unless you tell your users otherwise, its their own darn fault for getting in their and deleteing files, its like trying to plan: "What happens if s/he deletes my App.EXE file" you know?

>Hi,
>I want to tell you that your advice works correctly. Thank you.
>
>There is only one way that this solution won't work is when the user erase the foxuser.* files. If the user erases those files, the application creates another one and with the one created, the user will be able to print. I try to include the foxuser in my executable but it does not work. Do you know a better way to prevent any users to print?
>
>Salutations.