Jim,

Thanks for the thought. If I run the program from the command line, exit out, and then run it again, the performance degredation remains. It's only by exiting VFP that I go back to "normal" performance. Even if I issue a close tables all (or a close all, or a clear all, or a clear program, or a sys(1014), or a FLUSH(), or a bunch of other things), the symptom remains until I exit out of the VFP process entirely.

If I don't fix this soon, I think that's it for my hair!

Thanks again for the ideas!

David

>Don't know if this is applicable here, but some time back a similar severe slowdown was reported that was also 'cured' by a restart of the application.
>
>In that case the app was running lots and lots of SQLs and it was found that periodically doing a CLOSE TABLES ALL (well, I know it was closing all the tables but not sure that command was used) 'solved' the problem.
>
>good luck
>
>
>>David and Hilmar,
>>
>>Thanks very much for your input. David - I tried your program. Thank you very much. It's not finding any dangling references, but I'm still thinking that there is some sort of memory issue going on.
>>
>>If you're interested in more details, please see a response I posted under the same topic in the The Mere Mortals category. I'm getting some really wierd behavior.
>>
>>Thanks again for your help.
>>
>>David
>>
>>>>Hi All,
>>>>
>>>>I have a form with a 4-page pageframe, using a private datasession. In most cases, there are about 10-15 views open - most for lookup and populating lists, 4 for writing to data. Most times, the form works fine.
>>>>
>>>>However, in one situation, I open about 3 dozen more views. In particular, when deleting an object, I create a very deep containership hierarchy of business objects. Each business object checks it's contained objects to be sure that the deletion is OK to run. These objects then check their contained objects, and so on. This results in literally dozens of views being opened. The contained objects don't instantiate until needed (i.e. for the deletion). (I'm using Mere Mortals, and Mere Mortals Business Objects.)
>>>>
>>>>After performing this deletion, performance slows to a crawl, and the only way to restore it is to exit out of the app (or VFP) entirely.
>>>>
>>>>My initial thoughts were a dangling object reference, and I still leave that open as a possibility, but I can't find it anywhere.
>>>>
>>>>Does anyone else have any other ideas? Alternatively, any thoughts on how to find a dangling reference?
>>>>
>>>>Thanks,
>>>>
>>>>David
>>>>
>>>>(I'm also posting this message under The Mere Mortals).
>>>
>>>Closing and re-opening tables or views is slow. If you open them at startup (or keep them open after opening them) things should go faster.
>>>
>>>Another idea that occurs to me is that it might be better to leave the "delete OK?" issue to the database design, that is, use referential integrity.