<?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 Re: Prompt Errors in Add-in but not EG in Developers</title>
    <link>https://communities.sas.com/t5/Developers/Prompt-Errors-in-Add-in-but-not-EG/m-p/188615#M4400</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are talking about dynamic prompts with lists. &lt;BR /&gt;There is problem around that, not well known, not often hit. The behavior:&lt;/P&gt;&lt;P&gt;- the dynamic prompts are build before the real process is started.&lt;/P&gt;&lt;P&gt;- a SAS process must read the dynamic data using SAS metadata and accessing the data using a SAS process&lt;/P&gt;&lt;P&gt;- this prompt runtime building of that list is not executed in the same user-context / sas-session the real processing of the SP process is done. &lt;/P&gt;&lt;P&gt;&amp;nbsp; That one are defined after the prompt values are known.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;This effect can be seen having multiple appservers defined using the data and seeing the wrong appserver is opend at the moment of the prompt in EGuide.&lt;/P&gt;&lt;P&gt;This is a nasty design/implementation problem in the prompting framework possible having other erroneous effects.&amp;nbsp;&amp;nbsp; (difference WS/SP sas service)&lt;/P&gt;&lt;P&gt;There is no work around other than doing different coding avoiding that list.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Jul 2014 05:14:37 GMT</pubDate>
    <dc:creator>jakarman</dc:creator>
    <dc:date>2014-07-22T05:14:37Z</dc:date>
    <item>
      <title>Prompt Errors in Add-in but not EG</title>
      <link>https://communities.sas.com/t5/Developers/Prompt-Errors-in-Add-in-but-not-EG/m-p/188614#M4399</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone seen this type of behavior? :&lt;/P&gt;&lt;P&gt;SAS EG 5.1&lt;/P&gt;&lt;P&gt;I have created a fairly simple stored process that has 3 prompts (location, fault type, date range).&amp;nbsp; Originally I had all three in the same query builder.&amp;nbsp; Both the location and fault type were dynamic list prompts and have a lot of choices (968 for Location, 560 for fault type).&amp;nbsp; I allow the user to select up to 10 locations and 5 fault types to filter against and a date range. Everything works great when I run the STP in EG, but when I try to run it from Excel, I get a generic message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAS Add-In for Microsoft Office has encountered a problem&lt;/P&gt;&lt;P&gt;We recommend that you save your work and restart SAS Add-in for MS Office.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under Details:&lt;/P&gt;&lt;P&gt;Error creating window handle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I eliminated the prompt for fault type and hard coded that in, the problem went away and it worked fine from Excel.&amp;nbsp; Is anyone aware of prompt limitations within the MS Add-in framework? Is there a work around?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Fred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jul 2014 21:40:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Developers/Prompt-Errors-in-Add-in-but-not-EG/m-p/188614#M4399</guid>
      <dc:creator>FredGIII</dc:creator>
      <dc:date>2014-07-21T21:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: Prompt Errors in Add-in but not EG</title>
      <link>https://communities.sas.com/t5/Developers/Prompt-Errors-in-Add-in-but-not-EG/m-p/188615#M4400</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are talking about dynamic prompts with lists. &lt;BR /&gt;There is problem around that, not well known, not often hit. The behavior:&lt;/P&gt;&lt;P&gt;- the dynamic prompts are build before the real process is started.&lt;/P&gt;&lt;P&gt;- a SAS process must read the dynamic data using SAS metadata and accessing the data using a SAS process&lt;/P&gt;&lt;P&gt;- this prompt runtime building of that list is not executed in the same user-context / sas-session the real processing of the SP process is done. &lt;/P&gt;&lt;P&gt;&amp;nbsp; That one are defined after the prompt values are known.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;This effect can be seen having multiple appservers defined using the data and seeing the wrong appserver is opend at the moment of the prompt in EGuide.&lt;/P&gt;&lt;P&gt;This is a nasty design/implementation problem in the prompting framework possible having other erroneous effects.&amp;nbsp;&amp;nbsp; (difference WS/SP sas service)&lt;/P&gt;&lt;P&gt;There is no work around other than doing different coding avoiding that list.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jul 2014 05:14:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Developers/Prompt-Errors-in-Add-in-but-not-EG/m-p/188615#M4400</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2014-07-22T05:14:37Z</dc:date>
    </item>
  </channel>
</rss>

