At 01:48 PM 12/29/99 -0800, you wrote:
>I have a guess but I could not find any document to support my theory. I
>think what is happening is that you cannot guarantee that the FormPtr or any
>related with the form will be in the same memory address. The memory
>manager is constantly re-arranging memory chunks and I think this is
>happening with FormPtr. And I think that is the reason that always when you
>manipulate Form you make use of FrmGetActiveForm Function to acquire a valid
>FormPtr.
I can see how this would cause the memory pointed to by the form pointer to
be invalid, but it would not explain why the *value* of formPtr changes.
I could not see anything wrong with the code posted, please post code the
shows the context in which the class is instantiated and accessed.
Greg
Greg Winton
Bachmann Software and Services, LLC
mailto:[EMAIL PROTECTED]
http://www.bachmannsoftware.com
