Re: PFCSIG Message.stringparm Problem (Pb 7)

[Daniel Coppersmith]

Hmm...  if you haven't tried it, do a complete rebuild (maybe do two).  I'm assuming that you've confirmed that no changes were made that would cause an event other than open to be the first called... debugging from the call to open the window into the window events to make sure open is first...   ----- Original Message ----- From: PARAG-hotmail-pb To: [EMAIL PROTECTED] Sent: Saturday, January 29, 2000 1:00 AM Subject: Re: PFCSIG Message.stringparm Problem (Pb 7) we are taking it in open event only.and the major thing is that in the working pbl's(working pbl's are the pbls that are online right now) it is working fine the problem is only in the development pbls ----- Original Message ----- From: Daniel Coppersmith To: PARAG-hotmail-pb Cc: PFCSIG Sent: Friday, January 28, 2000 8:10 PM Subject: Re: PFCSIG Message.stringparm Problem (Pb 7) Is it possible something else is getting to it before your script?   What script are you getting the value of stringparm?  It should be the very first thing done in a window's open event, you need to override the ancestor script because otherwise pfc_preOpen will get it first.  Here's what your open script should look like:             // Override the ancestor to ensure safe arrival of the parameter         is_parmValue = message.stringParm         return super::event open()   Daniel ----- Original Message ----- From: PARAG-hotmail-pb To: [EMAIL PROTECTED] Sent: Friday, January 28, 2000 9:26 AM Subject: PFCSIG Message.stringparm Problem (Pb 7) hi all, i am having a serious Problem with message.stringparm.we had migrated from pb5 to pb7 .sometimes message.string parm works fine while in some cases it loses its value. is this a bug in pb7 and is there a workaround for this   Pl.Help Thanks in Advance Parag B.Bhagwat