Date:         Mon, 13 May 2002 08:22:28 -0400
Reply-To:     Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Subject:      Re: Protecting my programs

On Mon, 13 May 2002 12:48:13 +0100, Richard Simhon
<Richard.Simhon@CORNHILL.CO.UK> wrote:

>SAS-lers,
>
>I have a number of programs that are fairly long. To ensure that they are
>not inadvertantly deleted or changed, is there a way of protecting the
>program code either through some kind of password or some other form of
>protection.
>I am running on Windows NT using v8.1.
>Thanks in advance
>
>Richard Simhon
>Business Analyst
>Allianz Cornhill
>Tel 01483 55 2628
>
>
>
>**********************************************************************
>Copyright in this message and any attachments remains with us.  It is
>confidential and may be legally privileged.   If this message is not
>intended for you it must not be read, copied or used by you or
>disclosed to anyone else.   Please advise the sender immediately if
>you have received this message in error.
>
>Although this message and any attachments are believed to be free of
>any virus or other defect that might affect any computer system into
>which it is received and opened it is the responsibility of the
>recipient to ensure that it is virus free and no responsibility
>is accepted by Cornhill Insurance PLC for any loss or damage in any
>way arising from its use.
>
>Cornhill Insurance Plc, Registered in England number 84638,
>Registered Office 32 Cornhill, London EC3V 3LJ.
>
>Regulated by the Personal Investment Authority for life and pensions only.
>Member of the General Insurance Standards Council for general insurance
business.
>**********************************************************************



What is a SAS - program? SAS-BASE source, or SCL?
If you mean SCL, no problem: the user of your applications don't need the
source. He only needs the FRAMES, RESOURCES, ..., but not SCL. Even
PROGRAMs you can copy with the nosource option into a special catalog.
With other SAS sources I don't see a easy possibility. If you are using the
programs, you can also see the statements.
Ok, you could pack it into SCL code and compile it. Maybe that's a
possibility - if you have AF.