Re: NEWERA ixSuperField Problem
Posted in 1997
Mark, To my knowledge there won't be a event after data changed event, if you focus out from on super table to another, However if you focus out from one super field to another SF then there will be a ADCE. You have to understand NE does not post data events if you are moving from super field to non super field objects ( Even if it is Super Table ) e.g. check boxes, radio buttons some. On 1 May 1997, Markcampb wrote: } There are some cases where an after data changed event (ADCE) is not } triggered when you think it should be. If you move between super tables, } it does not trigger an after ADCE. If you have a supertable with just one } field, it will not trigger an ADCE there either. Those are the only two I } can think of off the top of my head. We have put all our validation code } into multiple locations in order to work around this. Whenever you } traverse a row in your grid form supertable, it should trigger an ADCE. I } know it does in our code. What are you doing when you don't get an event? } } } Mark Campbell } Concepts Dynamic Inc } markc@conceptsdyn.com } } In article <5ka50e$nfg$1@news8.gte.net>, Bret & Amy Lowry <blowry@gte.net> } writes: } } >Version: Newera 2.20 WC1 } >OS: Windows 95 } >Database: Informix SE6.0 & Informix On-line 7.12 } >I have a window with 2 supertables,one freeform, the other gridform. } >The grid form acts as a detail table to the freeform, I handle that in } >the code myself. } >Both supertables are defined as ixSupertables and all superfields are } >defined as ixSuperFields. } >The problem is that the only events that get posted for the superfields } >in the gridform supertable are: focusIn, beforeCell, afterCell and } >focusOut. } >I had been using the afterDataChanged event to perform some validations, } >after making changes elsewhere the event stopped being posted. } >I have double checked that the other events weren't inadvertantly } >reassigned at some point in the code...they aren't. } >I called Informix and they had one other reported case where this } >happened, there was no resolution. } >If anyone has any ideas or solutions I'd really appreciate it. } > } >Thanks } > } > } } }