I think you will have to code this, i.e: data _null_; file 'c:\test.htm'; put '' / '' / ' this is a button ' / '' / '' ; run; HTH Patrick ... View more

I believe for the first 3 measures a procedure like proc means or even proc tabulate would do the job. Just use your two variables with the conditions as classification vars. I'm having limited stats knowledge only, but isn't a t-test for comparison of 2 distributions only. As you're having balanced data I believe it's Proc ANOVA you're looking for. HTH Patrick ... View more

Are you sure this blank is not already stored this way in "base_path " before you pass it as a macro parameter? No clue why this might happen - but as UNIX paths never contain blanks a compress(base_path) might help. May be you also might want to use some of the additional "options" and remove all whitespace characters. HTH Patrick ... View more

I assume you would best save both date of interview and date of birth in your data - and then just replace the missing DoB in your older data via a merge over the id. You should provide an example with sample data if you need a more specific answer. ... View more

Not sure if I understand your data - and narratives are sometimes just too hard to read. Some example data would be helpful (i.e. you provide the first data step creating the data) and then show an example how the result should look like. Hope the following helps: data have; input case_id type_id complaint_code:$1.; datalines; 1 1 a 1 2 a 1 1 b 1 2 b 1 3 b 1 1 c 1 1 d 2 1 a 2 2 a 2 1 b 2 2 b 2 1 c ; /* data step version */ proc dataset data=have; by case_id complaint_code; run; data want(keep=Ncomplaints); set have end=last; by case_id complaint_code; if last.complaint_code then do; Ncomplaints+1; end; if last then output; run; proc print data=want; run; /* SQL version */ proc sql; create view haveV as select distinct case_id,complaint_code from have; select count(*) as Ncomplaints from haveV; quit; Regards, Patrick ... View more

There is an option in SAS EG that it doesn't open DS and output automatically. You also could programatically delete all the SAS DS which are only intermediary work DS. ... View more

Your requirement 2) sound to me like OLAP cubes. For requirement 1): If your customers are able to define what selection parameters they need then stored processes might be a good way. I assume that the needs and requirements will continuously change. Why not having/training up a few power users who are able to satisfy adhoc requirements via SAS EG and build/implement new stored processes for later ongoing needs? Cheers, Patrick ... View more

Where is SAS running (the SAS server): On your local machine or a remote one? Can you execute SAS code in batch on this machine? I believe for EG sessions (object spawner) the option noxcmd is the default. That's why you can't use shell escape commands like 'x'. I also believe the default for SAS batch processing is xcmd. As EG is only the client: Make sure your VBSCRIPT file is where the SAS server is. For more ideas: Please explain a bit more what you want to achieve and what you have. HTH Patrick ... View more

Hi SassyGirl SAS EG is a client. The SAS code is processed on the server. Using SAS EG: Are you observing this differences when executing the code on the server "local" (which then would be your PC SAS)? SAS EG might add some pre- and post- code before sending the code to the server - but I wouldn't know how this could lead to what you describe. I don't have SAS 9.2 at hand "right now" but I'm very interested if someone else with the same versions than you can replicate this behaviour. If yes: That would be something for Tech Support. Regards, Patrick ... View more

Hi Curtis I doubt that it's possible to capture an auto generated key while inserting rows. If there is a way then I would assume you should investigate SQL Server proprietary SQL syntax - and then load your data and read the key using pass-through SQL. May be an after insert trigger could do the trick - but that's something you would have to implement on the SQL server database itself. HTH Patrick ... View more

post deleted Message was edited by: Patrick ... View more

ranuni( ) proc means, proc tabulate, .... I.e: data RandomNumbers; do sample=1 to 100; do n=1 to 1000; RandomNumber=ranuni(0); output; end; end; run; And then use a procedure which allows you to calculate your values on different levels (like proc tabulate or proc means). proc tabulate data=RandomNumbers; class sample; var RandomNumber; table (sample all),RandomNumber*(mean std)*f=7.5; run; HTH Patrick Message was edited by: Patrick ... View more

input SampleID $ '1result'n '2result'n..... the syntax '...'n treats the string as a literal therefore allows you to use it as a variable name. You better rename these variables later on or you will have the same issue over and over. i.e. rename '1result'n = _1result; ...Ooops, sorry, didn't read your post good enough: For a fast solution: Use the import wizard in SAS EG and you will get what you need. The code generated by the import wizard will also give you some ideas how to solve this issue. Also worth a try might be options validvarname=any; (not sure if this will have any effect). HTH Patrick Message was edited by: Patrick ... View more

Hi Cathy There is definitely a SAS AMO for PowerPoint. Have a look at the product docu: http://support.sas.com/documentation/onlinedoc/addin/index.html I believe SAS AMO is a great way to empower end-users to do their own analysis and create some adhoc-reports without the need of knowing a lot about programming. For what you want to achieve I think that you risk a lot of pain when you give ppt slides to the end-user for regular reporting. It's less about the data source. I agree that you can protect it by granting read access only. But what are you going to do about the ppt slides which are under the end-users control? How do you avoid that your end-users start changing the slides until they are no more functional - and then start "screaming" that "the system" is faulty. I promise you that this is going to happen in one way or the other and that you will have to intervene and fix slides month after month. Also: Because a lot of end-users won't understand the difference between slides with a "data link" and their own "static" slides you risk a "inflation" of change request. You will get little understanding that some of the requested and so simple looking changes would be a pain to realise. If your end-users want access to the underlying data to produce their own adhoc-reports: Give them either access via SAS AMO (then best done in Excel) or produce monthly data extracts for them (i.e. csv files). There is another issue with SAS AMO (and also any VBA solution): All this stuff depends on the MS Office version and it wouldn't be the first time that some functionality doesn't work properly anymore after MS Office got updated. The "bad" thing about push and pdf: Unless you've got experience with SAS/Graph then creating reasonable graphs with SAS could become quite a challenge and is for sure more difficult than creating the same graphs in MS Office. HTH Patrick ... View more

Hi Cathy Refreshing the data "on0pen" or "onUserRequest" is already part of SAS AMO. A possible issue with your approach is that you need human intervention to refresh and distribute the monthly ppt slides. I personally would rather go for pdf output and create and distribute everything using SAS batch on the Unix server (job triggered by a scheduler). This approach requests no human intervention and is much more controllable. The other approach would be to distribute the ppt slides already to the end-users - and then these end-users can update their part of the slides (there might be some licensing questions with such an approach). To have the ppt refresh and distribution centralised so that a real person has to perform regular monthly tasks is not only a bit old fashioned but causes also regular repeating costs - not something a business likes. I actually see only one advantage in the "pull ppt" approach: The customer can customise the ppt slides later on according to their needs (but also mess them up...). HTH Patrick ... View more