Do cfd fields in an @dialogbox really cache data?

I am using (or at least trying to use) @dialogbox to display hidden and computed for display data to a user from various forms:

@DialogBox( “sfAN” ; [AutoHorzFit] : [AutoVertFit] : [NoCancel] : [ReadOnly] : [SizeToTable] : [OkCancelAtBottom] ; txtdocumentTitle )

The @dialogbox works fine the first time it is called from an open document, but if any data on the open document is changed and the @dialogbox called again the original data, not the new data is displayed. It is necessary to save, close and reopen the document for the changes to be available to the @dialogbox.

What makes it more strange is that if a field say dtDue is added to the subform used by @dialogbox and left editable (even though the @dialogbox is Read-only) the new value is displayed correctly when changed in original document BUT any CFD field in the dialogbox that uses dtDue say dtDueNext [Value: @Adjust(dtDue ; 1 ; 0 ; 0; 0 ; 0 ; 0)] it use the original dtDue value not the new one even though dtDue displays the new value in the dialogbox. !

Do cfd fields in an @dialogbox really cache data or is it just late and I should go home and try again tomorrow?

Subject: doh! … found a fix…

Even though the @dialogbox is READONLY you still need NoNewFields and NoFieldUpdate otherwise there is some caching going on.

@DialogBox( “sfAN” ; [AutoHorzFit] : [AutoVertFit] : [NoNewFields] : [NoFieldUpdate] : [ReadOnly] : [SizeToTable] : [OkCancelAtBottom] ; txtdocumentTitle )

Subject: …