> >>> Is Desktop =.T. on the parent form? Is the parent form modal?
> >> These are forms within the VFP main window. Both have Desktop = .F.
> > Modal or Modeless?
> Modeless.
Do you have a setfocus() or anything similar in code on the parent
form? Possibly in a timer?
--
Derek
__
Derek Kalweit wrote:
>>> Is Desktop =.T. on the parent form? Is the parent form modal?
>>>
>
>
>> These are forms within the VFP main window. Both have Desktop = .F.
>>
>
> Modal or Modeless?
>
>
>
Modeless.
--
Michael J. Babcock, MCP
MB Software Solutions, LLC
http://mbsoftwar
> > Is Desktop =.T. on the parent form? Is the parent form modal?
> These are forms within the VFP main window. Both have Desktop = .F.
Modal or Modeless?
--
Derek
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/m
Derek Kalweit wrote:
Viewletbuilder to the rescue to illustrate my dilemma!
http://mbsoftwaresolutions.com/demos/h2office/form_in_background_issue_viewlet_swf.html
>>> That looks like exactly what you'd see if the *Customers* form's (NOT the
>>> Account Information form
> >> Viewletbuilder to the rescue to illustrate my dilemma!
> >> http://mbsoftwaresolutions.com/demos/h2office/form_in_background_issue_viewlet_swf.html
> >>
> >
> > That looks like exactly what you'd see if the *Customers* form's (NOT the
> > Account Information form's) AlwaysOnTop is .T. Are you
Ken Dibble wrote:
>> Viewletbuilder to the rescue to illustrate my dilemma!
>> http://mbsoftwaresolutions.com/demos/h2office/form_in_background_issue_viewlet_swf.html
>>
>
> That looks like exactly what you'd see if the *Customers* form's (NOT the
> Account Information form's) AlwaysOnTop is
>
>Viewletbuilder to the rescue to illustrate my dilemma!
>http://mbsoftwaresolutions.com/demos/h2office/form_in_background_issue_viewlet_swf.html
That looks like exactly what you'd see if the *Customers* form's (NOT the
Account Information form's) AlwaysOnTop is .T. Are you sure that's not the
Dave Crozier wrote:
> Michael,
> Forgive me but I'm a little confused here. Maybe you aren't telling us
> something or I'm having a bad day, but I really can't see your problem here.
>
> FormA calls FormB and you want the FormB to
> (1) Appear on top
> and
> (2) get focus
>
> OK? Well I use this
D] On Behalf
Of MB Software Solutions
Sent: 17 May 2007 16:52
To: profox@leafe.com
Subject: Re: Want to activate child form launched in parent (but keep
parentopen)
MB Software Solutions wrote:
> Richard Kaye wrote:
>
>> How about loFrm.Show instead?
>>
>>
9 matches
Mail list logo