>>Gil,
>>Do you mean you can click on the original form? If so, then it sounds as if your second form isn't modal. Check with the debugger to see. There may be base-class code that 'unsets' your form setting.
>
>Barbara,
>
>Hi, as you suggested I checked the base class for my form to see if I was somehow unsetting the form settings as you mentioned; but nothing. I did have it as modeless, then I set it as modal. Still my form wouldn't stay on top. I had some code on the form's lost focus event that would deactivate it, but I got rid of it and nothing.

Gil, you can't change the setting from modeless to modal after the form is shown. Is it set modal in the properties BEFORE the form is opened?

>You know? I'm just getting tired of having to deal with all these little quirks that visual foxpro has. I spent, no, waste too much time trying to find my way around the objects when I should be concentrating on just data management. Object oriented objects should be there to make our lives easier, not more complicated. I like Fox for the speed and all the rest; I've been working with it for almost 8 years and I think I may need a change for a while...

Every time I start feeling that way (regularly, I assure you) I think of the OTHER languages I've worked in and how frustrated I was then too. VFP sure isn't perfect, but so far I've had better luck making it do what I need than other OOP languages I've tried ! A lot of the time it's still time spent forcing square pegs into round holes.

>Sorry for getting mellow,

Mellow is OK (mellow = relaxed, laid-back, comfortable) Venting your annoyance with VFP is OK too, but it isn't mellow. :-))