LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (February 1996, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Sun, 18 Feb 1996 15:52:22 -0800
Reply-To:   Robin Way <robin@BCINC.COM>
Sender:   "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:   Robin Way <robin@BCINC.COM>
Organization:   Barakat & Chamberlin, Inc.
Subject:   Re: Run Time under 6.11 for OS/2

Stephan Tobler wrote: > > I guess an answer to Charlie's question would be of great interest > for many of us. Till now I never heard about a runtime version or > compilation facility. Only tracing used modules and installing them > selectively cannot be the one an only truth. > Please let us now if SAS provides some enhancements to create > executables! Are there official statements?

<snip>

Stephan, thanks for clarifying your interest in the "run-time" version of SAS. According to a conversation I had with Rick Langston about a year and a half ago, the RTV (run-time version) does require you to track the DLLs that your application uses, and then to distribute these to your client. You had caught all these details to date. What has apparently not been mentioned is the financial/legal/support details between the app developer, the client, and SAS Institute. The client need not license SAS software; the app developer needs to negotiate with SI re/the licensing fee to distribute specific DLLs on the client's behalf; and SI will not provide Tech Support to the client--this is the responsibility of the developer.

Now, if this scheme has been updated since my conversation with Rick, or if I am omitting/misstating relevant details, I apologize in advance. I think these are important pieces of information for anyone interested in developing and distributing apps. Please contact me for further information on my own perspectives on app development using SAS-based tools, but as the above represents a total brain dump on this issue, I'm afraid I'm not the person to ask for further clarification on SI policies and procedures.

Thanks again for your interest in more information.

Robin Way Barakat & Chamberlin, Inc. Portland, Oregon robin@bcinc.com


Back to: Top of message | Previous page | Main SAS-L page