I have to admit I am stumped. I have a MDI child window loaded from a CLICK event on a button on the main window. The child window has no custom READ event specified. Some of the prompts on the child window have a custom ICONV/OCONV conversion, which has been tested thoroughly. When I send a READ event to the child window via a menu entry on the MDI parent, I get a debugger break in the conversion routine for each prompt that has the conversion routine, without any explanation. Changing the name of the conversion routine produces the same results. The call stack looks like this:

DATECONV

RTP19

FORMREAD

SEMANTICLOGICLAYER

$$$SYSPROG*READ.WINDOW.OIWIN*

RUN_EVENT

SEND_EVENT

EXECNPHANDLER

$$$SYSPROG*..OIWIN*

RUN_EVENT

Could someone please explain what is going on, and what the problem might be? As an OI novice, I would be very grateful.

Thanks,

Peter

Peter,

I know you said that these routines have been thoroughly tested but are you sure there aren't any exceptions where a debug statement may have been left behind?

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Donald,

As usual, you were right on the money. A recheck of ALL the code, including symbolics being loaded by the window, turned up an errant DEBUG in a symbolic, put there by an idiot programmer (me) :(. I wasted a whole day looking elsewhere. Thanks for the help.

Peter

Peter ..

I'll offer you a tip, if you don't already know it.

It's very difficult to debug a dictionary call (if that's what you're doing) with a debug statement. If it's in a stored proc, then it's relatively easy. Almost all of my dictionary symbolics call external code for that reason.

Don Miller

C3 Inc.

Don,

Thanks for the tip. I appreciace your help as I further my knowledge of OpenInsight.

View this thread on the forum...