I still think you're very unclear with your question. It might be complex, but taking the time to elaborate is the only way you'll get solutions that work.
You mention DDE and XML. Are you using Tagsets? Are you using DDE? Why both?
Second, Are your Microsoft "Trust Settings" set up appropriately. I have a job here, and every time we set up a new user the template has to be set up as a trusted document for them.
Whosack you proved the SAS environment is running on both used id's.
Very nice because this eliminates that possible parts.
As all is working at SAS do not expect miracles being solved by upgrading. Although every support will tell you this.
"The next version will solve every problem, just wait" .... (humbug)
One of te last possibilities is something strange/weird in the batch scheduling you do and your manual actions as difference.
This beyond the scope of SAS and yet the should know. (google at microsoft for this type of questions)
Some examples:
- Run Powershell script as Scheduled task, that uses Excel COM object
What could be the issue is the running key when started as scheduled job does not have the needed rights or resources.
- the scheduler is running by a key, probably "local server".
+ This key can not elevate rights.
+ some reources may have other settings (com is an example may be more)
- When running scheduled it is missing the keybord / screen resources. These do exist when used directly.
+ when some program is expecting those resources (call for them) then ... (wait/dump)
Why should SAS support know? Anser: It is common for Windows.
http://technet.microsoft.com/en-us/library/hh125927(v=ws.10).aspx
It is the same reason you have to change some rights (logn as batch job etc.)
I was able to get things working. First, I discovered that a SAS program that calls an excel macro that draws charts using data output by SAS works in batch. That is it works in batch if I set up a scheduled task using my ID and password. If I set it up to run without providing a password it does not run. This same code does a save.as xls then erases the xlm file.
However, the vbscript program I wrote to do the conversion still did not work.
A couple weeks ago I had some free time and I wrote an excel macro to do the same thing as the vbscript. It works fine and converts the xml files to xls (I had a client that could not open xlsx files on his computer so I can not use that format.
I would still like to know what 9.4 adds to ODS. I heard a couple times from people that it is much improved
I would still like to know what 9.4 adds to ODS. I heard a couple times from people that it is much improved
Check out What's New in the Output Delivery System for 9.4.
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.