I have a record that spans multiple MDI child forms. From the MDI frame I use a push button to execute a procedure that, in turn, makes calls to several other procedures. These procedures were originally written in AREV and most of them refer to @Record.

So far, I have encountered problems when trying to refer to @Record in OI. Maybe it's because of the whole MDI thing – I'm not sure.

What is the best way to handle @Record in OI under these circumstances? I have thought about reading the record during the click event of the push button (the button that gets the whole thing rolling) on the MDI frame and then setting @Record programmatically. Is this a good solution, or should I consider something else?

Thanks.

Greg,

Of all the MDI apps we work on, only one actually spans multiple child windows for the same record simultaneously. In this situation we are maintaining a user defined property of the MDI Frame with the current contents of each child window.

I wouldn't recommend using @RECORD since OI will still update it on its own.

[email protected]

SRP Computer Solutions

Don,

What about setting up a common variable to contain the data normally contained in @Record? Would it be more efficient to create a common variable than to use a user defined property as multiple procedures will need access to the record contents?

Thanks,

Greg

Greg,

Take your pick. In the end you will either add a COMMON statement to all of your routines or you will retrieve the value of a user-defined property. In the end, the amount of support code will be very close.

[email protected]

SRP Computer Solutions

I can think of one case where user defined properties is easier: when you have more than one instance of the window, and the various instances have different rows. (Not so common in an app with MDI perhaps.)

One case where common block might be easier is where you want to keep the data even after you closed the window.

- Oystein -

View this thread on the forum...