|
|
 |
| found 36 articles for 0.303 sec |
  |
Group: alt.news.macedonia · Group Profile · Search for Doc9 in alt.news.macedonia
Author: SN
Date: Dec 25, 2008 11:50
I have used those methods successfully with both the IntrNet App Dispatcher and the SAS 9 Stored Process server. Are you using the STPSRV_HEADER function as documented in the Issues section of: http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/inet2stp.html If so and it is still not working, can you post the code where you were using those methods and they did not work? Regards
|
| Show full article (6.04Kb) |
Group: comp.softsys.sas · Group Profile · Search for Doc9 in comp.softsys.sas
Author: Don Henderson
Date: Aug 21, 2008 16:10
On 1 Jul., 22:58, donaldjhender...@HOTMAIL.COM (Don Henderson) wrote: Xavier, Not sure I agree with your summary. Stored Processes can produce any type of output - and you are correct that the type of content to be generated depends on the client. That is the reason that SAS provides the STPBEGIN and STPEND macros for use in your Stored Processes. Those macro's generate the "appropriate"
|
| Show full article (1.47Kb) |
|
Group: comp.softsys.sas · Group Profile · Search for Doc9 in comp.softsys.sas
Author: Don Henderson
Date: Jul 2, 2008 05:35
You should read that documentation : http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/inet2stp.html (or http://tinyurl.com/69do59) Stored Process are not providing HTML, it provides XML (Tagset SASREPORT11 for example) The reason is that the client controls the behaviour of the Stored Process : For a same STP inside Word it's RTF, inside Excel it can be CSV or formatted etc.
|
| Show full article (4.98Kb) |
|
|
|
1 ·
2 ·
3 ·
4 ·
next |
|
|
