Desktop productivity for business analysts and programmers

while using "saveas" enterprise guide is creating short cut to the file.

Reply
Occasional Contributor
Posts: 13

while using "saveas" enterprise guide is creating short cut to the file.

Hi Everyone -

 

when we use "saveas" option on sas program to save the file in desired location. By default it is creating as shortcut on the file name.

 

i have copied  the EGP file to different location it is still looking for the old path. 

 

Is there a way to make the sas program as permanent file when we using "Saveas" ?

 

Thanks in advance!!

 

 

SAS Employee
Posts: 68

Re: while using "saveas" enterprise guide is creating short cut to the file.

Hi @Durga_SAS

 

If you save the project directly (instead of saving the program), you won't have to individually save your programs.

Said that, in your case, you can go to the program's properties (right-click) and from the General view, you can click on the Embed button.

Embed.JPG

 

I hope that helps you.

 

Cheers,
Damo

Occasional Contributor
Posts: 13

Re: while using "saveas" enterprise guide is creating short cut to the file.

Hi Damo- Thanks for your reply.

 

i have clicked on embedded option as mentioned below and saved the egp file. the file path is still showing as old location in the properties.

 

thanks.

SAS Employee
Posts: 68

Re: while using "saveas" enterprise guide is creating short cut to the file.

Hi @Durga_SAS

 

Which version of EG are you using?

 

With EG7.1, this is what I have after I click on the EMBED button.

  - Button is greyed out

  - File path shows "(Embedded In Project)" instead of the previous location

Embed2.JPG

 

Cheers,
Damo

Occasional Contributor
Posts: 13

Re: while using "saveas" enterprise guide is creating short cut to the file.

I have tried it again. it is working as expected. thanks alot for your help!!
Esteemed Advisor
Posts: 6,685

Re: while using "saveas" enterprise guide is creating short cut to the file.

Enterprise Guide has two ways of storing code

- internally ("Embed") in a project file

- externally as a .sas file anywhere that can be reached either on the desktop or through the IOM bridge to the workspace server.

If SAS code is stored externally, the code is represented in the project as a link to the file; this means that for retrieval of the code, the means of storage (server connection, file system) must be accessible to the EG instance where the project is opened.

One thing you can do:

- store programs in the same path where the project is stored, or in a subdirectory thereof

- set the file links to "relative" in File / Project Properties. This only works when everything is stored locallly on the desktop.

 

The option I like to use is the following:

- set up a central location for codes on your SAS server

- have a filesystem link to that location in every EG user's home directory

- save code to the server, using that link in Server - SASApp (or whatever your Application Server is named) - Files

If you now promote your project to other users, the path to the codes will look the same for them, and they can find the codes that are linked to from the project.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
Ask a Question
Discussion stats
  • 5 replies
  • 122 views
  • 3 likes
  • 3 in conversation