topic Re: I am trying to call excel macro from sas 9.3 EG connection from my local server. But I am getting the following error in the initial step itself of opening a excel. I am new to SAS DDE, please help me in SAS Programming

I am trying to call excel macro from sas 9.3 EG connection from my local server. But I am getting the following error in the initial step itself of opening a excel. I am new to SAS DDE, please help me

ruchiy — Tue, 29 Jul 2014 12:08:51 GMT

I am trying to call excel macro from sas 9.3 EG connection from my local server.

But I am getting the following error in the initial step itself of opening a excel. I am new to SAS DDE, please help me

17 %sysexec md "&path.Report";

18 options noxwait noxsync obs=max;

_______

ERROR 13-12: Unrecognized SAS option name NOXWAIT.

18 ! options noxwait noxsync obs=max;

_______

ERROR 13-12: Unrecognized SAS option name NOXSYNC.

19 X "'C:\Program Files (x86)\Microsoft Office\Office14\EXCEL.exe'"

19 ! ;

Re: I am trying to call excel macro from sas 9.3 EG connection from my local server. But I am getting the following error in the initial step itself of opening a excel. I am new to SAS DDE, please help me

Kurt_Bremser — Wed, 30 Jul 2014 07:13:15 GMT

Are you positively sure that you are connected to a workspace server on windows?

This error usually occurs on non-Windows platforms.

What happens if you do a simple

X "dir";

Re: I am trying to call excel macro from sas 9.3 EG connection from my local server. But I am getting the following error in the initial step itself of opening a excel. I am new to SAS DDE, please help me

RichardinOz — Wed, 30 Jul 2014 12:13:05 GMT

Microsoft DDE only works when both the application issuing the DDE statements and the target application are on the same Windows platform. Typically, when using SAS EG, the core SAS application resides on a server (which may or may not be a Windows server) but the Excel instance is on a local machine. SAS EG, even though it is located locally, is not itself involved in DDE; it merely issues SAS code to the server to be executed. Use EG file import/export to move data between Excel and SAS.

Despite its many merits, (and many champions), DDE is legacy technology which, as you have found, is not scalable in a client server (EG) situation. Microsoft and others did toy with the idea of making it more generic but it didn't happen and we now have to find repoacement methods.

I have some sympathy for you if you have been given some code to run. You can only make DDE work if you have Base SAS (and Excel) installed on your desktop, or you can adapt the code to work on a Windows server where you have SAS. If your workplace can provide that, good. Otherwise you have been set a task you cannot complete.

Richard.

Re: I am trying to call excel macro from sas 9.3 EG connection from my local server. But I am getting the following error in the initial step itself of opening a excel. I am new to SAS DDE, please help me

ruchiy — Wed, 06 Aug 2014 12:04:58 GMT

I am not getting anything

its simply saying

19 X "dir"

19 ! ;

23 %LET _CLIENTTASKLABEL=;

24 %LET _CLIENTPROJECTPATH=;

25 %LET _CLIENTPROJECTNAME=;

26 %LET _SASPROGRAMFILE=;

28 ;*';*";*/;quit;run;

29 ODS _ALL_ CLOSE;

32 QUIT; RUN;

Re: I am trying to call excel macro from sas 9.3 EG connection from my local server. But I am getting the following error in the initial step itself of opening a excel. I am new to SAS DDE, please help me

Kurt_Bremser — Wed, 06 Aug 2014 12:15:18 GMT

Issuing

X "dir";

in my local SAS session (not EG) resulted in an open cmd window with the contents of the directory listing and a prompt (issued without noxwait).

Open your Server list, right mouse click on the active server, tab "Software", "View Initialization Log". This may give you a clue where the server actually resides.