Paul,

> The application is an MDI application. the child form in question is
> created and released from the stack, then after it's released, (using
> the release statement), and the main child form becomes active, it
> explodes. But so far it's after I modify a record. For the two
> variables involved, neither looks like a sane value.

Unfortunately I don't use MDI ever so I don't know if there is something
about this that could be tripping you up.

> Now there is another MDI child form that is set up to work the same,
> and it doesn't give me an error. I am going to look at the
> properties, and make sure that they match up. If it's a property
> difference, I will let you know which one works, and which one
> explodes.

Thanks, that will help.

> > This suggests to me that there is either an uninitialized variable or
> > that something has performed an invalid write to memory and trashed
> > some of it. I am in favor of the thought that something is getting
> > trashed somehow.
>
> Gee I didn't think Delphi did that, then again anything is possible.

This would be a bug in IBO most likely.

> > What I need is a reproducible test case that duplicates this problem
> > and then I can look at it.
>
> > I have been somewhat buried in things lately so I am not certain when
> > I could have the problem resolved. I suspect in your efforts to
> > isolate this you will hopefully solve it while you are at it.
> >
> > Keep us posted on your progress and in the meantime I will keep in the
> > back of my mind what could be causing this.
>
> Will do, not sure how much I will do today, my wife spent the last
> month dying of a cold, now I have it, and had to cancel two important
> appointments today..... I may spend the afternoon watching Star Trek
> re-runs on the Space channel. I hear the remote calling me....

Take care and get your family well!

Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com