Add OnGotFocus vba WITH vba

[oneidalake]

I have a form with a button that adds a field to another form using vba CreateControl.

I want to set the OnGotFocus Event Procedure of that new field.

For example, the new field that was created is called test123 within Form "ABC".

I want to use vba to create a vba statement for test123 so when I view the code for form ABC, there is a newly created line that says...

Private Sub Test123_GotFocus()
MsgBox "Hello"
End Sub

Any ideas?

Thank you,
Jim

 

[Galaxiom]

See the Module.InsertLines Method

 

[moke123]

something like this

Dim strFormOpenCode As String
Dim mdl As Module

Set mdl = Forms!Form1.Module     'reference your form module

strFormOpenCode = "Private Sub Test123_GotFocus()" & vbCrLf & "MsgBox" & """Hello""" & vbCrLf & "End Sub"
 
With mdl
 .InsertText strFormOpenCode
 End With

 

[Mark_]

Personally I'd do a hide/disable OR unhide/enable rather than create. This lets you deal with the control at all times, especially if you need to know what its value is, without testing first to see if it has been created.

 

[moke123]

not to mention lifetime limits with form controls.

 

[oneidalake]

Thanks for all the responses.

I ended up going with Moke123's suggestion that worked flawlessly!

Also, this will be rarely used and will have definite limits. Will only be used in case they need an extra field or two.

Thanks again!!!
Jim

 

[Mark_]

Thanks for all the responses.

I ended up going with Moke123's suggestion that worked flawlessly!

Also, this will be rarely used and will have definite limits. Will only be used in case they need an extra field or two.

Thanks again!!!
Jim

I'd test rather extensively. As I understand, creating a control at run time counts against the number of controls that can be created on a single form (something like 750ish), so if it stops working suddenly you may know the cause.

 

[moke123]

what mark said, and you may also have a problem in an mde or accde.

 

[oneidalake]

I'd test rather extensively. As I understand, creating a control at run time counts against the number of controls that can be created on a single form (something like 750ish), so if it stops working suddenly you may know the cause.

Thanks. I was just toying around with something and this one part was driving me crazy. I'll test it out. Although this particular form has quite a few controls (150 or so), I can't imagine adding more than a dozen with this method.

Thanks to you both.
Jim

 

[Galaxiom]

Although this particular form has quite a few controls (150 or so),

Hmmm. So many controls often suggests the data structure might not be the best.