Hi All,

By looking for a bug in my application (MM 7.0), I introduced a 'set step on' command in the BizObject's GetDataAccessObject() method to do some investigation.
In this method, the following command can be found:

loDataAccess = This.oDataEnvironment.GetCursorObject(tcAlias)

I found out that when it executes, the GetCursorObject method of the
oDataenvironment executes without any problem: When it reaches the end
and the last command 'RETURN loCursorX' has to be executed, loCursorX is still a real object reference.

When the program control is returned to the calling GetDataAccessObject method however, all of a sudden, the loDataAccess has become a NULL
When I then removed the 'set step on' command, there was no problem anymore.
This made me think that running the debugger at that point influenced
memory space or something like that.
It looks as if I 'm missing something fundamental here.
Can someone help me on this?


Mark