Ted Roche wrote:
>> But I don't want it to be a modal form. Your example is just that
>> (since you use the 1 for the Show parameter value).
>>
>
> That's just the kind of wanton immodality that leads to... DotNet!
>
> These kids today!
>
>
To quote the caveman from the commercials "Yeah I
On 5/17/07, MB Software Solutions <[EMAIL PROTECTED]> wrote:
> But I don't want it to be a modal form. Your example is just that
> (since you use the 1 for the Show parameter value).
That's just the kind of wanton immodality that leads to... DotNet!
These kids today!
--
Ted Roche
Ted Roche &
MB Software Solutions wrote:
>
> But I don't want it to be a modal form. Your example is just that
> (since you use the 1 for the Show parameter value).
>
>
Well, make the 1 a 2 then.
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance:
MB Software Solutions wrote:
> Richard Kaye wrote:
>
>> How about loFrm.Show instead?
>>
>>
> Actually, I'm already doing that (and so that's not it):
>
> LPARAMETERS tlActivate
> IF NOT EOF(this.cCursor) THEN
> LOCAL loFrm as Form, liCustID as Integer, lcName as String
> liCustI
Alan Bourke wrote:
> You could change the child form to a form class instead. Then on the
> parent form:
>
> Local oChildForm
>
> oChildForm = CreateObject("myChildFormClass")
> oChildForm.Show(1)
>
> x1 = oChildForm.Property1 && Query a property set when the form
> was running
>
You could change the child form to a form class instead. Then on the
parent form:
Local oChildForm
oChildForm = CreateObject("myChildFormClass")
oChildForm.Show(1)
x1 = oChildForm.Property1 && Query a property set when the form
was running
oChildForm.Release()
__
Not sure if this will help, but here it is. Try it after loFrm.Activate()
ACTIVATE WINDOW (loFrm.Name)
Also, you might want to add NOSHOW to the DO FORM command.
-Original Message-
From: MB Software Solutions
Sent: Thursday, May 17, 2007 10:51 AM
Richard Kaye wrote:
> How about loFrm.Sh
Richard Kaye wrote:
> How about loFrm.Show instead?
>
Actually, I'm already doing that (and so that's not it):
LPARAMETERS tlActivate
IF NOT EOF(this.cCursor) THEN
LOCAL loFrm as Form, liCustID as Integer, lcName as String
liCustID = EVALUATE(this.cCursor + ".iid")
lcName = ALLTRIM(
Tracy Pearson wrote:
> Does the parent form have "AlwaysOnTop" set true?
>
No, but I don't want it to Always be OnTop, either.
--
Michael J. Babcock, MCP
MB Software Solutions, LLC
http://mbsoftwaresolutions.com
http://fabmate.com
"Work smarter, not harder, with MBSS custom software solutio
B Software Solutions
Sent: 17 May 2007 13:34
To: Profox
Subject: Want to activate child form launched in parent (but keep parent
open)
frmParent form has code that does a DO FORM frmChild NAME loFrm and
then I do a loFrm.Activate, but the frmParent stays in the foreground
and the frmChild is i
How about loFrm.Show instead?
MB Software Solutions wrote:
> frmParent form has code that does a DO FORM frmChild NAME loFrm and
> then I do a loFrm.Activate, but the frmParent stays in the foreground
> and the frmChild is in the background. I want frmChild to get front
> focus.
>
> 'frmChil
Does the parent form have "AlwaysOnTop" set true?
-Original Message-
From: MB Software Solutions
Sent: Thursday, May 17, 2007 8:34 AM
frmParent form has code that does a DO FORM frmChild NAME loFrm and then I
do a loFrm.Activate, but the frmParent stays in the foreground and the
frmChild
Is the child set to be in top level form ? Setfocus() ?
Allen
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of MB Software Solutions
Sent: 17 May 2007 14:34
To: [EMAIL PROTECTED]
Subject: Want to activate child form launched in parent (but keep parent
frmParent form has code that does a DO FORM frmChild NAME loFrm and
then I do a loFrm.Activate, but the frmParent stays in the foreground
and the frmChild is in the background. I want frmChild to get front
focus.
'frmChild.Activate' didn't do it...what would?
--
Michael J. Babcock, MCP
MB
14 matches
Mail list logo