The screen is too large - Too Many ACCESS Statements

[Joe Boyle]

could it be related to qkgo settings - I'm thinking of the expression size
parameter in particular  ... but there was also selection size, secondary 
blocks, rollback size ...

----- Original Message ----- 
From: "Deskin, Bob" <Bob.Deskin at cognos.com>
To: "Rohde, Dirk" <Dirk.Rohde at vpgroup.com>; "Darren Reely"
<darren.reely at latticesemi.com>
Cc: <powerh-l at lists.sowder.com>
Sent: Thursday, April 06, 2006 6:00 PM
Subject: RE: The screen is too large - Too Many ACCESS Statements


> Unfortunately this sort of thing will vary with what components the
> screen uses. I don't believe that it's not simply the number of ACCESS
> statements or the number of PATH choices. It could be the overall amount
> of procedure code generated, the overall size of the expression
> processing area, etc. Some of this is dynamic and fluid in terms of
> actual limits. That's why it's almost impossible to say exactly what
> caused the screen to become too large. And since these limits are buried
> in the architecture of the product, it would be difficult to change.
> That said, if there's a repeatable case, it may be worth reporting to
> customer support so we can analyze the screen. And certainly, let us
> know if something compiles in one version and not in the next.
>
> Bob
>
> -----Original Message-----
> From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
> [mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On
> Behalf Of Rohde, Dirk
> Sent: April 6, 2006 12:05 PM
> To: Darren Reely
> Cc: powerh-l at lists.sowder.com
> Subject: RE: The screen is too large - Too Many ACCESS Statements
>
>
> We have hit this error in Axiant with what is our largest screen in
> terms of code. Cognos was not able to provide us with anything specific
> that is required to resolve this issue other than telling us that we
> need to reduce the amount of code. Every time we encounter this error,
> we try to track down and remove any unused code, try to rewrite what we
> can so that it is smaller, or move code to either another screen or the
> database.
>
> Dirk Rohde
> VantagePoint Systems Inc.
>
> -----Original Message-----
> From: powerh-l-bounces+dirk.rohde=vpgroup.com at lists.sowder.com
> [mailto:powerh-l-bounces+dirk.rohde=vpgroup.com at lists.sowder.com] On
> Behalf Of Darren Reely
> Sent: April 5, 2006 4:14 PM
> To: powerh-l at lists.sowder.com
> Subject: The screen is too large - Too Many ACCESS Statements
>
> I hit an interesting error today. I received a single Qdesign error that
> said "The screen is too large".
>
> I received this because I was trying to allow for all of the possible
> combinations for 6 field entries during the FIND processing. I like
> flexibility. Of course I used ACCESS statements on my file, which is
> actually a cursor. Excluding the last field reduced the ACCESS count and
> allowed the screen to compile without an error. That reduced the
> generated PATH count down to 16 from 25.
>
> Has anyone hit this problem before and can anything be done about it.
>
> Darren
> P.S. This isn't critical. The screen will be more than fine for the user
> base.
>
> -- 
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = Mailing list:
> powerh-l at lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request at lists.sowder.com
> Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
>
> -- 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request at lists.sowder.com
> Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
>
>     This message may contain privileged and/or confidential information.
> If you have received this e-mail in error or are not the intended
> recipient, you may not use, copy, disseminate or distribute it; do not
> open any attachments, delete it immediately from your system and notify
> the sender promptly by e-mail that you have done so.  Thank you.
>
> -- 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request at lists.sowder.com
> Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
>