The answer to your question lies in the post you have made: Warning: Apparent symbolic reference TEMP not resolved.  This means the macro variable TEMP is not being created.  Thus something is amis with the code (perhaps you are running on another OS or in a system where the environment variable does not exist): data _null_; temp = sysget('temp'); * Put the environment variable %temp% in SAS \ variable temp call symput ('temp', right(trim(temp))); * put the content of temp in the SAS macrovariable &temp; run; However, more importantly, this thread is 3 years old.  Start a new thread with your question, inputs, outputs, test data etc. I would advise against the use of VBS script as it may not work with your system. Are you trying to read in an Excel file?  No information to work with, hence why posting a full question would be betteras we have no idea what you are doing or how. ... View more

Hi, do bear in mind this topic was closed 6 years ago.  Its a good idea to open new questions as things will have changed in that time. In terms of will the data be the same when imported back, the answer is it will retain the data part, however anything SAS specific will not, so if you export: A   B  C 1   2   3   You will get a dataset with columns named A,B,C, and one row of data 1,2,3, but you will not necessarily get the right length, format, informat.  And also depending on language settings/special characters etc. the data might be different too. ... View more

The functionality we are discussing is in the Subject of the question, "Deleting rows in Excel", which is why I suggest ods is not useful.   I have never, ever recommended to use DDE?   Excel's front end far exceeds most other fronts ends (Forms, text, etc.), drag and drop, formula fill, filtering, functions etc. make it very quick and easy.  This of course comes at the cost of anyone who uses anything other than the front end.  Hence why I don't recommend to use it as data storage. ... View more

Well, you could look at doing by case; With case being a variable which splits the graph. But your second question may not work then.  Behind the scenes sgplot and others create graph template language, you can see this by updating your code: PROC SGPLOT DATA = filename tmplout="c:\gtl_code.txt"; The file c:\gtl_code.txt will show you what GTL is created by your sgplot.  I mention this as it gives a fair bit more freedom, for instance you can have dynamic variables and all kinds of conditionals.    In terms of your specific part, I would highly recommend reading through the thousands of examples in: https://blogs.sas.com/content/graphicallyspeaking/ Its the best resource for all graphing, with examples in sgplot, gtl.  You will likely find something similar to what you want and can start with that. ... View more

Could you confirm the functionality of this DDE replacement?  From what I see it is only for creating Excel files, much like the rest of the ODS system.  It doesn't for instance, have the ability to go into existing Excel files and make alterations, at least from what I could see.   My original post still stands, Excel has its pluses, its a great frontend for data entry and such like, but it is not a good backend.  If you have to work with Excel files, then its perhaps a good idea to invest some time in learning Open Office, an dperhaps other tools like C# or python which can alter directly existing files.  ODS Excel is good for writing out data from SAS to Excel, but thats really about it.    I would really consider what the purpose is, look at data, data entry, and reporting as different elements as there a many ways of doing each and not necessarily one which is great at all of them.  ... View more

Thats odd, can't think of anything directly unless you had a long line which split, or some sort of special character or break.  Cant find a system option for it.  When I do: data temp; put 'line 1' //; put 'line 2'; run; I get: line 1 <- <- <- line 2 The reason being is that / moves the cursor to the first char of the nest row, as does put.  So print line 1, move to next (/), move to next (/), move to next (put), print line 2.  So two / should effectively create two blank rows. ... View more

Not tested (pop test data in the form of a data step please): data want; set have; retain num_times 0; if lag(flag)=0 and flag=1 then num_times=sum(num_times,1); run; Last record would have your total number of times.  You could also do it via sql to join lowest previous date to current record as well. ... View more

Exactly.  How can you bring in things which aren't text.  Checkbox could be a PDF object, or a picture.  End of the day, you could learn javascript in PDF and export it, or possibly find a third party library to get it (perhaps at a quick search: https://stackoverflow.com/questions/55777812/python-pdf-how-to-read-from-form-elements-like-checkbox), but its going to take a fair bit of effort.  Go back to source data is really the best option. ... View more

You could simply scan the last word by space, and check if length is 1 or 2: data want; str="abc ert werty we"; if lengthn(scan(str,-1," ")) in (1,2) then check=1; run; ... View more

PDF is a proprietary binary file.  SAS cannot read much else other than the plain binary code which unless you understand and can parse it, is of no use.  PDF is not a data format, its a render destination.  Whilst there are certain packages in python/R and other languages languages to do certain things, even if you do manage to get anything useful out of it would require full QC and probably a lot of work/processing.  I would highly recommend either returning to source data which is the preferred method, or worst case, type things in manually.  Ultimately PDF is a dreadful format, as far from open as possible, so avoid it as much as possible. ... View more

Your post does not include enough information to help answer the question.  Posting test data in the form of a datastep is required.  For instance, there is no example of what dod or adt is?   Your text is all in opposites, you say dod is numeric, but line 221 is clearly telling you an issue as you have compress() which requires a text var, with dod var which is numeric. Also, there is no error, only telling you you have differing types for your variables.  If its not working, try simplifying your code down, only do one function per run, e.g. see what the compress does, then what the inputs do, this is stepwise error analysis.  Only build up long complicated multi calls when you know bits work. ... View more

Not tested, but something like: %let x =%nrstr(f588c556-15c4-4d59-b9df-88b2c655a950,06d54597-fc35-459b-bc5e-1075e9643a1d,06d54597-fc35-459b-bc5e-2137e9643a1d); data want; do i =1 to countw("&x.",","); result=scan("&x.",i,","); output; end; run; Essentially count how many comma separated items, then substr each by delimiter comma and output.   To add, macro variables are not th eplace to store data, there are many ways to store it, json, xml, datasets etc. ... View more

I would advise to split the program logic out.  Something like three distinct steps Get data Process data Report data   So in your example, I would process the survey data such that you get a dataset out from it: ods output <object>=workingdata; proc surveyfreq data=surveydata missing nosummary; stratum stratum; weight FinalWt; tables cohort*(q0001 q0002)/cl nostd; run; In the above you would need to get the object name from an ods trace on; statement which will show you all the objects which are created (ods trace off; after).  The objects can all be saved and processed further - this is a big plus to the process as you can format and manipulate as you want. Then when you have the data all nicely processed, then open the Excel ods and report the data.  ... View more

Interesting that after all this time they have made DOCX a destinatation.  I would still however stand by my original posts.  RTF being a far better format for outputs.  The reasons, RTF is markup, you can insert markup via report, or in data, its open, plain text file format makes it machine and programmatically readable, can be opened and parsed just like a word document.  So has all the functionality, without the drawbacks of docx (which is a zip file with XML parts).  If you need PDF from it, you can directly convert to PDF from RTF.  Only if there was no other option would I be generating docx off the bat. ... View more