Jeremy,

I hacked it together after answering the Nth question about dangling object references a couple of years ago. *g* I'm glad you've found it to be useful.

I'll have to look at the code when I get home, I thought it would check for object array properties but maybe it isn't. It won't be hard to add that functionality to it.

If your array only had .t. or .f. in the rows, the array wasn't holding the reference. It was somewhere else, which could easily happen when you are passing object references around.

If you are using PEMSTATUS() there is a bug when you use it more than once in the same line of code that will cause VFP internal object references that you can't get rid of at all. Perhaps this is what you are running into. There is nothing the ObjRef tool can do to find these kind of dangling refs.

>>What kind of dangling object reference couldn't it find? I might need to work on an update to the tool.
>
>What I had was an object that had an array that stored the "Enabled" properties of an object of the form. So, it looked like this:
>
>MyObject.ioObjects[1] = .T.
>MyObject.ioObjects[2] = .F.
>MyObject.ioObjects[3] = .T.
>etc...
>
>But, I guess since I assigned these when I init'ed MyObject with a parameter of my form (toContainer), It assigned these items by reference instead of value (I'm assuming).
>
>So, I don't know if you could do much about that, BUT... If there are objects references in an array, does your tool check in that array?
>
>Anyway, it's a great tool - since I've shown it to people at work, I've gotten several requests for the program (and this was the day of getting it).