Screen Linkage Parameters

[Peter Bateman]

Mark:

I think Darren is on to something. That it works in development but not in 
production.
would indicate that the databases or ownership structures are not in sync.

I simple difference like NOT NULL on one column in development but not on 
the same
named column in development could make the difference.

Regards,
Peter



>From: "Bruin, J.M. de" <Bruin@WT.TNO.NL>
>To: "'Darren Reely'" <darren.reely@latticesemi.com>,   
>"'powerh-l@lists.sowder.com'" <powerh-l@lists.sowder.com>
>Subject: RE: Screen Linkage Parameters
>Date: Thu, 29 Apr 2004 08:48:42 +0200
>
>Darren,
>
>could there be a difference in the record LAYOUT?
>Though it might be that the actual record length matches the in development 
>and
>production there might be a redefinition (f.i.) that's bothering you.
>Did you try compiling both calling AND called screen?
>
>Mark
>
>-----Original Message-----
>From: Darren Reely [mailto:darren.reely@latticesemi.com]
>Sent: donderdag 29 april 2004 3:15
>To: 'powerh-l@lists.sowder.com'
>Subject: Screen Linkage Parameters
>
>
>Hi all,
>
>I'm getting the following error.
>
>        *d* The screen linkage parameters sizes are incompatible.
>
>Normally this is easy to figure out because the size of the items being
>passed do not match. In this case the size of the file record being
>passed does match. I have confirmed via QShow and an Oracle Describe
>that the table is identical.  I even performed a diff on the QShow
>output. The table has not changed since before the earlier compiled code.
>
>I have tried compiling the screen both in production and development. In
>either case, the error appears in production. When I compile in
>development and execute there, it works. The difference is the calling
>screen in development is a more recent compile from a current project we
>are working on. Moving the current production screen to development
>displays the same error.
>
>Any ideas or experience about what can be throwing this out of sync?
>Perhaps a dictionary change in development not brought forward into
>production? Oracle table changes such as indexes?
>
>Here are the code snippets:
>
>;CALLING SCREEN
>file lot_step_summ in mfg
>...
>procedure designer gilf &
>   help "Generate ILF lot id."
>begin
>   run screen inv_gilf mode e passing lot_step_summ
>   display ilf of lot_step_summ
>   let t_need_update = "Y"
>end ;
>
>CALLED SCREEN
>file lot_step_summ in mfg master
>...
>screen inv_gilf activities find, change, entry &
>   receiving lot_step_summ &
>   on line 10 for 14 message on line 24 &
>   mode at 2,2 action at 2,9
>
>
>We are running Powerhouse 8.23.D7
>on Solaris 2.8 (SunOS 5.8)
>with Oracle 8.1.7.4.0
>
>
>I have discussed this with Cognos. We were unable identify the cause.
>
>I'll likely have to recompile the calling screen, but it too is a called
>screen. So I'm looking to find the root cause.
>
>Thanks for any suggestions.
>
>Darren
>
>
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to
>powerh-l-request@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@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to 
>powerh-l-request@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.

_________________________________________________________________
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines