04-18-2017 11:30 PM
04-19-2017 09:26 AM
You never addressed why you would use DDE? I assume it's because if licensing issues?
You dont need the DDE for the CSV file.
For the XLSX file what happens when you run the connection string alone? I'm assuming it doesn't connect and Excel doesn't open so work on fixing the DDE statement. What version of Excel do you have? If it's 2013+ I have heard cases where DDE was no longer functional.
Look at the different DDE options for connections.
Post a screenshot of the error you receive.
04-19-2017 04:18 AM
As others have stated there is not enough information for us to debug. What I would however state is that DDE is old - very old. It was discontinued over 10 years ago and is really not recommended for use on anything now. In certain setups it doesn't work at all. I would really advise that you change your data handling policy, for instance is there a reason why you read in the data this way, rather than saving the data to CSV, there doesn't appear to be any funky Excel specific things going on as you are reading from first data row/column to end, so no reason to try any Excel specific things. Depending on the file you may even get away with just:
libname tmp xlsx "<path to your file><yourfile>.xlsx";