07-25-2013 11:54 AM
Is there a reason to not wanting handing over te code?
Is the release/change process missing? That would an issue to solve,
This is meaning you develop have let it tested and someone else after an user-acceptance will test it.
In this kind of processes the handing over is done with all kind of agreements on responsabilities.
Do you want to have your code run while you are not present. No releasemanagement involved, than the question is: can your program being scheduled. Answer: There are a lot of schedule options.
It depends on the technical enviroment versions tools and the support that is delivered to you.
By the way versioning is something quite different as release management.
07-25-2013 12:43 PM
Absolutely not :smileyhappy: ....on the contrary it's very advanced and efficient.
If it's as fancy as you claim then I would think you would want all to see it.
07-25-2013 07:58 PM
We are using the SAS BI environment and some of our users run stored processes, with user-modifiable parameters, via SAS Add-in for Microsoft Office (AMO). The underlying SAS code for each stored process is called from an SVN repository, which only we (the IT people) can modify. Users do not have access to the SVN repository, and cannot see the underlying SAS code (except via log output). However, log output can be suppressed so that the user cannot see source code statements in the log.