|Subject||RE: [IBO] TIBOQuery - master child relationship|
> From: "Alan McDonald" <alan@...>you must be a sensitive new-age guy, Woody, for these factors to translate
> >> Sounds more like a bug in the reporting software. I have never,
> >> nor will I
> >> ever, use persistent fields. They are a PITA and cause more
> problems than
> >> they solve, IMHO.
> > fascinating - why? what problems?
> Persistent fields are OK as long as your data schema doesn't
> change much, if
> any. There are also many problems that people have had on these
> related to persistent fields using the fields editor that they
> forgot about,
> etc.. To me, it's just as easy to assign events, formatting, etc.
> to fields
> during the AfterOpen event of a dataset.
> Woody (TMW)
into PITA and "more trouble than it's worth"
Anyway, I have uploaded an example of the issue (artifact).
Add and remove the persistent field DEPT_NO from IBOQuery1, then run the app
WITH the pesistent field, the employee grid is filled.
WITHOUT the pesistent field, the employee grid is empty.