Frank,

>But I think You should be
>
>1. It saves a lot of writing
>2. The lines get shorter esp. when deeply referencing
> into object-hierarchies
> (Thisform.pageframe1.page2.cnt1.buttonx.Caption =
> iif(Thisform.pageframe1.page2.cnt1.List(Thisform.pageframe.P....)))
>3. thus is much more easy to debug.
>4. You are much more flexible when deciding to move either
> objects or methods (eg. from page1 to page2)
>5. I've heard that processing can be faster
>6. Despite the f... case I just ran into I've never had any
> drawbacks.

Your points are well-taken, and I have thought about them all...

WHat I dislike are very large WITH...ENDWITH blocks where you forget what is being WITHed. Also, I used to work on Delphi code that another developer created. In Delphi, a "with" can include several objects, and then the compiler knows what reference applies to which object. In Delphi, you don't even need a period in front of the property or method you are accessing, so code like the following was common in Delphi:

with qry, frm, textbox
myvar = SQL
myothervar = height
andyetanother = text
end;

There was no way to know what object went with what property (until I got to know Delphi a LOT better), and it is just hard to read. I know VFP is much easier, but I have been inside huge WITHs that are just hard as heck to follow. Don't get me wrong, I do use WITHs, especially with deep container hierarchies and with ListBoxes (some of those commands get LOOOOng without a WITH)

I am zeroing in on the problem. I have it isolated to only a few times when it occurs (and a couple of them appear identical, yet one scenario lets the screen hang and the other lets it close), so it is all very interesting. Hopefully I will know more tomorrow, but for now I need to go to the doctor (don't worry, the troubleshooting hasn't made me ill, just a routine check-up... *smile*)

Have a great afternoon!

>Regards from Berlin (Sunshine 22°C)

Regards from Des Moines, Iowa (Sunny and 60 degrees F)

Later,
JoeK