08-11-2011 12:48 AM
At present I have a situation where some data is being stored on an Excel (2007) workbook and periodically imported into
SAS Enterprise Guide 4.1 (126.96.36.1996) with the Import Task.
I realise what is going on behind the scenes when I run the Import task for the first time in a SAS session is that an asterisk-delimited text file is created on the server hosting my SAS session and the Import Task does its work from that copy of my original Excel workbook.
However, if, whilst still running that same SAS session, I update and save the Excel workbook and re-run the Import Task, my changes are not reflected in the
asterisk-delimited text file or the resultant SAS dataset that is produced by the Import Task.
The only way around this that I have found so far, is to close down the SAS session and re-start a new one. When I run the Import Task for the first time in that new session, a fresh look is taken at the underlying Excel workbook and my resultant SAS dataset reflects the updates that I made.
Does anyone know a way around this without resorting to Proc Import?
08-11-2011 05:39 AM
This is probably the most annoying thing I've came across in EG.
What seems to work is if you save and close your project (but don't disconnect your session or close EG), then reopen it. This seems to be enough to trick SAS into reloading the file from source.
That's still pretty bad in terms of usability, so I normally sidestep EG's own import process wherever possible and FTP files to our SAS server.
08-11-2011 05:40 AM
Oh, we're using SAS Enterprise Guide 4.1 (188.8.131.529) so I can't say for certain it'll work in your version, or that SAS haven't fixed this properly in a later version!
08-11-2011 01:17 PM
We had faced the same issue . The problem arose due to some patch that was installed. Contacted the tech support and they were able to resolve it. You should do the same
Need further help from the community? Please ask a new question.