<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic %WINDOW statement alternative in SAS/EG in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437058#M28216</link>
    <description>&lt;P&gt;Hi there.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are currently migration from PC/SAS to SAS/EG V7.1 and have faced a problem in respect to supporting existing usage in autoexec's.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Today user are prompted to rung in DEV, TEST or PROD through %WINDOW statements in order to&amp;nbsp;set up right pointers to e.g. ExaData.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;%WINDOW is not supported in SAS/EG, so we have been looking into prompts. But prompts are used in specific projects and not as part of a startup. The prompt can be excuted by opening of a project with a prompt in it, but it has to be triggered.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So what we are looking for is a way to excute a prompt in "batch", so to include the&amp;nbsp;code/funktionality in an "normal" autoexec as part of the EG initialization.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone solved this I'm very interested to hear how this was accomplished.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers, Lars&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 14 Feb 2018 11:55:26 GMT</pubDate>
    <dc:creator>Rishoej</dc:creator>
    <dc:date>2018-02-14T11:55:26Z</dc:date>
    <item>
      <title>%WINDOW statement alternative in SAS/EG</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437058#M28216</link>
      <description>&lt;P&gt;Hi there.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are currently migration from PC/SAS to SAS/EG V7.1 and have faced a problem in respect to supporting existing usage in autoexec's.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Today user are prompted to rung in DEV, TEST or PROD through %WINDOW statements in order to&amp;nbsp;set up right pointers to e.g. ExaData.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;%WINDOW is not supported in SAS/EG, so we have been looking into prompts. But prompts are used in specific projects and not as part of a startup. The prompt can be excuted by opening of a project with a prompt in it, but it has to be triggered.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So what we are looking for is a way to excute a prompt in "batch", so to include the&amp;nbsp;code/funktionality in an "normal" autoexec as part of the EG initialization.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone solved this I'm very interested to hear how this was accomplished.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers, Lars&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 11:55:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437058#M28216</guid>
      <dc:creator>Rishoej</dc:creator>
      <dc:date>2018-02-14T11:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: %WINDOW statement alternative in SAS/EG</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437059#M28217</link>
      <description>&lt;P&gt;Why not just have a "Startup" project which gets loaded first, does all the prompts, then loads the appropriate project?&amp;nbsp; I haven't used EG for years, but that would seem logical to me.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 12:00:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437059#M28217</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2018-02-14T12:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: %WINDOW statement alternative in SAS/EG</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437065#M28219</link>
      <description>&lt;P&gt;Well that woul be a valid solution, but as I'm aware of you are not able to specify an EG project that has to be executed as part of the startup.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are able to specify SAS statements as part of the startup/initialization, but i need to fire up an EG project not just ordinary SAS statements.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers, Lars&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 12:24:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437065#M28219</guid>
      <dc:creator>Rishoej</dc:creator>
      <dc:date>2018-02-14T12:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: %WINDOW statement alternative in SAS/EG</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437196#M28229</link>
      <description>&lt;P&gt;In our installation, we had multiple profiles for each system and when we logged in it made us select the desired profile each time.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/29811"&gt;@Rishoej&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;Well that woul be a valid solution, but as I'm aware of you are not able to specify an EG project that has to be executed as part of the startup.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You are able to specify SAS statements as part of the startup/initialization, but i need to fire up an EG project not just ordinary SAS statements.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers, Lars&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 16:23:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/437196#M28229</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2018-02-14T16:23:02Z</dc:date>
    </item>
    <item>
      <title>Re: %WINDOW statement alternative in SAS/EG</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/441121#M28458</link>
      <description>&lt;P&gt;If you haven't already seen, checkout Chris' blog post on autoexec options&amp;nbsp;in EG:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://blogs.sas.com/content/sgf/2014/05/01/autoexecs-the-sas-enterprise-guide-advantage/" target="_blank"&gt;https://blogs.sas.com/content/sgf/2014/05/01/autoexecs-the-sas-enterprise-guide-advantage/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Mar 2018 05:16:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/WINDOW-statement-alternative-in-SAS-EG/m-p/441121#M28458</guid>
      <dc:creator>CaseySmith</dc:creator>
      <dc:date>2018-03-01T05:16:51Z</dc:date>
    </item>
  </channel>
</rss>

