> From: Rob_James@UMANITOBA.CA [mailto:Rob_James@UMANITOBA.CA]
> I have written some SAS code within my dissertation that
> "may" have some
> commercial value... probably not, but why not delude myself. I'm just
> testing the waters right now.
> My question is this: Can I provide the macro to clients without them
> being able to see the underlying macro code? Alternatively, are there
> ways to "secure" the software from prying eyes, to make sure it only
> runs for licensed periods, etc.
<sigh> not a problem I have, as a federal employee.
They pay me to do this, which includes providing all these freebies!
So: how to hide the code:
* store the macro(s) in a macro catalog
search our most excellent archives for other posts on the techniques
keywords: autocall, /store
option: MautoSource MStored SASMSTORE
I don't think the macro catalog can be hacked, that is: reverse engineered,
to see the code.
you better have this thing nailed down, because updating stored macros is
* write the macro(s) to a catalog
you can then load them by %include
obviously easy to get back to the code by any S.A.S. aficionado
%include ... /source2;
REMEMBER WHERE THE SOURCE CODE IS!
Ron Fehd the macro maven CDC Atlanta GA USA RJF2@cdc.gov
OpSys: WinNT Ver: 8.1
---> cheerful provider of UNTESTED SAS code!*! <---
By using your intelligence you can sometimes make your problems twice as
-- Ashleigh Brilliant