Replacing pointer to SAS dataset to preserve dependent tasks

[SunilGupta]

Hi,

I have a situation in which the dataset is moved to another directory.  In my project file, is there a way for me to repoint to the dataset in the new directory without losing all of the tasks that depend on the dataset?  I would hate to manually recreate all queries and rerun tasks to reproduce the results with the updated dataset.

Thanks,

Sunil

[Patrick]

Hi Sunil

EG projects have file extension .egp but are actually zip files. You can open your eg project file with WinZip. You should then find a project.xml file in the zip archive.

Bit of a hack but: just modify the relevant path in this xml file and things should work again.

HTH

Patrick

[Doc_Duke · Accepted solution]

In addition to Patrick's comment, I'd add that this situation is exactly why one should use libraries to point to SAS datasets in EGuide.  Move a project and just change the libname and you are back in business.

[Patrick]

Never tried it but eventually the migration wizard also allows you to re-map datasets:

C:\Program Files\SAS\EnterpriseGuide\<4.2 or 4.3>\MigrationWizard.exe

[SunilGupta]

Thanks for your replies to my question.  I will try these options and in the future, use libnames to reference datasets instead of pointing to them. 

[SunilGupta]

I modified the project.xml file but must have missed something since Enterprise Guide could not open the file.  I will make sure to use libnames next time.  I assume once I apply libnames, I need to create a temp version of my datasets so that I can select it before running a task?  I can not open the dataset directly using the libnames to make it active?

[Doc_Duke]

For that one, the answer is "it depends".  If you store the output data in a permanent library, then you can use it directly.  If you store it in the WORK library (the default for Query Builder in 4.3), then you would have to rebuild it each time.