Date: Sat, 1 May 2010 13:39:25 +0000
Reply-To: goladin@gmail.com
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Murphy Choy <goladin@GMAIL.COM>
Subject: Re: How can I read .egp files without SAS EG?
In-Reply-To: <201005011313.o41AmoGc003751@malibu.cc.uga.edu>
Content-Type: text/plain; charset="utf-8"
Hi Art,
Can you help me to check with birdie whether the egp if corrupted can be rescued using a zip repair program?
Sent from my BlackBerry Wireless Handheld
--
Regards,
Murphy Choy
Certified Advanced Programmer for SAS V9
Certified Basic Programmer for SAS V9
-----Original Message-----
From: Arthur Tabachneck <art297@NETSCAPE.NET>
Date: Sat, 1 May 2010 09:13:42
To: <SAS-L@LISTSERV.UGA.EDU>
Subject: Re: How can I read .egp files without SAS EG?
Note from birdie:
"EG projects are ZIP archives, and any program capable of opening or
extracting the archive can be used to open the project file."
Art
---------
On Fri, 30 Apr 2010 08:56:18 -0700, Sterling Paramore <gnilrets@GMAIL.COM>
wrote:
>I often use emacs to write SAS code, but run everything through EG (v
4.2).
>It's a bit clunky at times, but it's the only way I can conceive of
managing
>a large multiple-source-file code base. The key is that I don't embed the
>.sas files in EG. Instead, they're linked to a location on my shared
>network drive (could be a local space too). You can open up a file from
>your local drive just by using File->Open->Program.
>
>One catch is that when EG "opens" the source file (e.g., when you
>double-click on the program node), any changes made to the source code by
>your external editor are not immediately read. In order for EG to read
>those changes, you have to "close" the source file. This means clicking
the
>little "x" in the upper right of the window (NOT the BIG X that closes EG,
>just the little one that closes the source code window). This doesn't
>remove the source code from your project, it just removes the source code
>form EG's memory, so that the next time it tries to run the code, it will
be
>re-read from the source file. The clunky bit is that I can't always
predict
>when EG will open the source file. Sometimes it happens after running the
>code, sometimes it doesn't. To be safe, I usually open the source file
and
>then close it prior to running.
>
>An even clunkier problem happens if your program is saved/opened from the
>SAS server. In this case, the program is only read into EG once. If you
>make any changes to the source code with an external editor, they will not
>be read even if you use the "closing" trick described above. If you need
to
>do this, the best way to get EG to re-read the source is to right click on
>the program node, select properties, then change the file path to exactly
>what it is. This will force EG to re-read the source into memory.
>
>Some of these directions may be a little different if you're using
something
>other than version 4.2.
>
>Hope that helps,
>-Sterling
>
>
>On Fri, Apr 30, 2010 at 7:46 AM, Matthew Wilson <matt@tplus1.com> wrote:
>
>> Hi --
>>
>> I know I can fire up SAS Enterprise Guide to read the code within a
>> .egp file, but I don't want to do that. Instead I want to use my own
>> editor.
>>
>> Is this even possible?
>>
>> Thanks in advance.
>>
>> Matt
>>
>>
>>
>> --
>> W. Matthew Wilson
>> matt@tplus1.com
>> http://tplus1.com
>>
| 
