Referencing problem

[cmd]

I have code in the OnExit event of a control on a subform. The code
works properly in this instance. If, however, I put the same code in
the OnExit event of a control on a Tab Control of a main form, the code
errors out at the 2nd line. The error number is 13 and the description
is "Type mismatch". Both controls are memo fields. I suspect that
"Screen.ActiveC ontrol.Parent" is not referencing the form as intended.

Thanks for any help,
Mark
'************** *******
Dim frm As Form
Set frm = Screen.ActiveCo ntrol.Parent
If frm.Dirty = True Then
frm.Dirty = False
End If

'(rest of the code)
'************** *******

[Allen Browne]

The Parent of a control is not necessarily the form.
It could be the tab control (your example), or another control (e.g. for an
attached label), or an option group (for a button in the group), or another
form (for a subform control), and so on.

Perhaps you could use use Form.ActiveCont rol, or pass a reference to the
control if you are calling a generic procedure.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<cm*@mountain.n etwrote in message
news:11******** **************@ s13g2000cwa.goo glegroups.com.. .

>I have code in the OnExit event of a control on a subform. The code
works properly in this instance. If, however, I put the same code in
the OnExit event of a control on a Tab Control of a main form, the code
errors out at the 2nd line. The error number is 13 and the description
is "Type mismatch". Both controls are memo fields. I suspect that
"Screen.ActiveC ontrol.Parent" is not referencing the form as intended.

Thanks for any help,
Mark
'************** *******
Dim frm As Form
Set frm = Screen.ActiveCo ntrol.Parent
If frm.Dirty = True Then
frm.Dirty = False
End If

'(rest of the code)
'************** *******

[cmd]

Thanks Allen, but I'm lost.

I checked my copy of the Access97 Developer's Handbook, 3rd ed. and
found several cautions against using Screen.ActiveCo ntrol and
Screen.ActiveFo rm. The suggestion was to use Me properties instead. But
"Me" isn't applicable in a global function -- right?

In this case, I don't think there's a problem using
Screen.ActiveCo ntrol, but there is trying to reference the
ActiveControl's form by using Screen.ActiveCo ntrol.Parent or
Screen.ActiveFo rm.

"Parent" is this case appears to be the TabControl or Page of the
TabControl on which the ActiveControl exists -- rather than the subform
itself.

I wasn't sure how to use your suggestion (Form.ActiveCon trol) -- I
tried using:

If Form.ActiveCont rol.Dirty = True Then
Form.ActiveCont rol.Dirty = False
End If

.... but I get an "object doesn't support this property or method"
error.

Thanks,
Mark
Allen Browne wrote:

The Parent of a control is not necessarily the form.
It could be the tab control (your example), or another control (e.g. for an
attached label), or an option group (for a button in the group), or another
form (for a subform control), and so on.

Perhaps you could use use Form.ActiveCont rol, or pass a reference to the
control if you are calling a generic procedure.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<cm*@mountain.n etwrote in message
news:11******** **************@ s13g2000cwa.goo glegroups.com.. .

I have code in the OnExit event of a control on a subform. The code
works properly in this instance. If, however, I put the same code in
the OnExit event of a control on a Tab Control of a main form, the code
errors out at the 2nd line. The error number is 13 and the description
is "Type mismatch". Both controls are memo fields. I suspect that
"Screen.ActiveC ontrol.Parent" is not referencing the form as intended.

Thanks for any help,
Mark
'************** *******
Dim frm As Form
Set frm = Screen.ActiveCo ntrol.Parent
If frm.Dirty = True Then
frm.Dirty = False
End If

'(rest of the code)
'************** *******

[Keith Wilby]

<cm*@mountain.n etwrote in message
news:11******** **************@ m79g2000cwm.goo glegroups.com.. .

"Me" isn't applicable in a global function -- right?

PMFJI ... it is available if you pass the form object to the function.

Call libSomeFunction (Me)

libSomeFunction (frm As Form)

Regards,
Keith.
www.keithwilby.com

[RoyVidar]

"cm*@mountain.n et" <cm*@mountain.n etwrote in message
<11************ **********@m79g 2000cwm.googleg roups.com>:

"Parent" is this case appears to be the TabControl or Page of the
TabControl on which the ActiveControl exists -- rather than the
subform itself.

You'd probably need some errorhandling, but try out this idea

Dim frm As Form
Dim ctl As Object

Set ctl = Screen.ActiveCo ntrol
Do While Not TypeOf ctl Is Form
Set ctl = ctl.Parent
Loop

If TypeOf ctl Is Form Then
Set frm = ctl
Else
MsgBox "ouch"
End If

--
Roy-Vidar

[cmd]

Thanks RoyVidar,

.... Debug.Print Screen.ActiveCo ntrol gives me the value of the control,
rather than the control name or type -- is "Set ctl =
Screen.ActiveCo ntrol" still what I want?

Thanks,
Mark

RoyVidar wrote:

"cm*@mountain.n et" <cm*@mountain.n etwrote in message
<11************ **********@m79g 2000cwm.googleg roups.com>:

"Parent" is this case appears to be the TabControl or Page of the
TabControl on which the ActiveControl exists -- rather than the
subform itself.

You'd probably need some errorhandling, but try out this idea

Dim frm As Form
Dim ctl As Object

Set ctl = Screen.ActiveCo ntrol
Do While Not TypeOf ctl Is Form
Set ctl = ctl.Parent
Loop

If TypeOf ctl Is Form Then
Set frm = ctl
Else
MsgBox "ouch"
End If

--
Roy-Vidar

[cmd]

Help! This is getting pretty frustrating and it seems that it shouldn't
be that much of a problem!

The spellcheck function (in a global module) which I have been using
works fine for controls on a mainform/subform layout. The function is
placed in the relevant controls' OnExit event. Spellcheck occurs as the
user tabs out of each field. Warnings are turned off during the event
to suppress the "Spellcheck is complete" message. The code is as
follows:

Dim frm As Form
Set frm = Screen.ActiveCo ntrol.Parent
If frm.Dirty Then
frm.Dirty = False
End If

On Error Resume Next

Dim L As Integer
L = Nz(Len(Screen.A ctiveControl), 0)
L = Len(Nz(Screen.A ctiveControl, ""))
If L 0 Then
With Screen.ActiveCo ntrol
.SetFocus
.SelStart = 0
.SelLength = L
End With

DoCmd.SetWarnin gs False
DoCmd.RunComman d acCmdSpelling
DoCmd.SetWarnin gs True
End If

This global function, however, does not work as is on a
mainform/subform/tabcontrol layout. The procedure does not recognize
"Screen.ActiveC ontrol.Parent" as the subform on which the
control/tabcontrol is placed -- hence, it errors at the line: "Set frm
= Screen.ActiveCo ntrol.Parent".

I can live without using this global function for layouts where I have
a subform with a tabcontrol on the subform. Therefore, I thought I
would try using the code as a local procedure and placed the code in
the OnExit event for a specific control on the tabcontrol of the
subform. I changed "Set frm = Screen.ActiveCo ntrol.Parent" to: "Set frm
= Me.Form" and apparently this works for this portion of the code.
Spellcheck works as it's supposed to, but the focus will not leave the
control. An error-handler reports the error number as "0" and there is
no error description.

I added a statement at the end which returns the focus to the
tabcontrol:
"Screen.ActiveC ontrol.Parent.S etFocus" and this resolves the problem of
getting stuck in the control. However, it also prevents the user from
simply tabbing from one field to the next.

I've tried other variations of spellchecking routines placed as a local
procedure for each control, but the focus also stays locked on the
current control -- e.g.:

(I changed "PreviousContro l" to "ActiveCont rol" since I wanted it to
run as an OnExit event, rather than from a command button.)

'************ Code Example 1 Start *************** *
' Adaptation by Terry Wickenden of code
' from Microsoft Knowledge Base

Private Sub cmdSpell_Click( )
Dim ctlSpell As Control

Set ctlSpell = Screen.Previous Control
If TypeOf ctlSpell Is TextBox Then
If IsNull(Len(ctlS pell)) Or Len(ctlSpell) = 0 Then
MsgBox "There is nothing to spell check."
ctlSpell.SetFoc us
Exit Sub
End If
With ctlSpell
.SetFocus
.SelStart = 0
.SelLength = Len(ctlSpell)
End With
DoCmd.RunComman d acCmdSpelling
Else
MsgBox "Spell check is not available for this item."
End If
ctlSpell.SetFoc us
End Sub
' *************** *** Code Example 1 End *************** *****

[David W. Fenton]

cm*@mountain.ne t wrote in
news:11******** *************@h 48g2000cwc.goog legroups.com:

... Debug.Print Screen.ActiveCo ntrol gives me the value of the
control, rather than the control name or type -- is "Set ctl =
Screen.ActiveCo ntrol" still what I want?

Since you'll be calling the external function from a context where
Me is meaningful, pass the control reference to your function. Then
test its parent until you get to its parent form:

If TypeOf ctl.parent = Form
ctl.parent.Requ ery
Else
ctl.parent.pare nt.Requery
End If

That's air code, so you'll have to change it appropriately to work
in all cases.

This method completely avoids the Screen.Activeco ntrol issues, which
I have never trusted.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[cmd]

Thanks David for the response
.... but, "requery"?
.... I must be way over my head here because I have no idea what I would
be requerying.
Mark

David W. Fenton wrote:

cm*@mountain.ne t wrote in
news:11******** *************@h 48g2000cwc.goog legroups.com:

... Debug.Print Screen.ActiveCo ntrol gives me the value of the
control, rather than the control name or type -- is "Set ctl =
Screen.ActiveCo ntrol" still what I want?

Since you'll be calling the external function from a context where
Me is meaningful, pass the control reference to your function. Then
test its parent until you get to its parent form:

If TypeOf ctl.parent = Form
ctl.parent.Requ ery
Else
ctl.parent.pare nt.Requery
End If

That's air code, so you'll have to change it appropriately to work
in all cases.

This method completely avoids the Screen.Activeco ntrol issues, which
I have never trusted.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

cm*@mountain.ne t wrote in
news:11******** **************@ m79g2000cwm.goo glegroups.com:

... but, "requery"?
... I must be way over my head here because I have no idea what I
would be requerying.

I thought the context was requerying the parent form.

I just saw your other post about spell checking. I don't quite
comprehend why you'd want to spell check something in this fashion,
nor do I know if it's possible do to this with a subform.

However, I do know that you should be able to test what type of item
the .Parent is and then conditionally execute different code. The
parent of a control on a subform is the subform control, and you'd
want to find the name of that, and then use it to get a form
reference.

If Me.Parent is subform control and it is named "MySubForm" , you'd
refer to it as:

Me.Parent.Paren t("MySubForm"). Form

If the parent is a tab, you'd use:

Me.Parent.Paren t

to return a reference to the form the tab is embeded in.

If the tab is on a subform, you'd use:

Me.Parent.Paren t.Parent("MySub Form").Form

Make sense?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/