Get record field value from general module

[GraeagleBill]

I have a general module that needs a field value from the current record in a known form that has just had one of its record selectors given focus. So far, I've not hit upon the proper syntax:

lngRegID = Forms("frmRegistry").ActiveControl.Form([RegistryID])

Not even sure I'm in the right "ball park"?

[moke123]

Can't you pass the value or control name to the sub?

[Micron]

I think you're expecting the ActiveControl to be a subform control. Is that the case, and is it even possible?
Form(RegistryID) seems wrong too.
What is the design setup/hierarchy?

[GraeagleBill]

The Public Function gets called via a Right-Click CommandBar entry. There's not the usual direct access to record objects like a single-click on a form's Record Selector would be, so one has to obtain the record's field values with a different method, I'm just struggling a bit to figure out how to do that.

In A2003, the problem didn't exist, as the Public Function for the Right-Click "On Action" could be located in the form's module and the form's controls and record field values were readily accessible in code, but that went away with the A2003

[GraeagleBill]

Normally yes, but with CommandBar "On Action" from a Shortcut menu the world changes a bit and I'm tying to adjust to the difference.

[davegri]

I just ran into a similar problem last week. I changed a stand-alone form to a subform and discovered that the custom right-click target function (in the subform's module) no longer worked. The function was trying to open another form. So I did as you did. I made a new right-click menu command to call a new defined function in a general module. That function had one line of code to call the ORIGINAL right click target function (now no longer a commandbar called function) in the subform.
All pops, no bangs.
Call Forms.frm_Main.[ctlSubform].Form.TargetFunction

The target function in the subform must be Public.

In A2003, the problem didn't exist, as the Public Function for the Right-Click "On Action" could be located in the form's module and the form's controls and record field values were readily accessible in code, but that went away with the A2003

Probably did exist if the form was a subform.

[June7]

lngRegID = Forms("frmRegistry").ActiveControl.Form("RegistryID")

'or

lngRegID = Forms("frmRegistry").ActiveControl.Form.RegistryID

'or

lngRegID = Forms("frmRegistry").ActiveControl!RegistryID

[GraeagleBill]

All three forms you suggested failed with the same error.


Function xfrDelReg is the "On Action" property of the CommandBar. Function DelReg is the original unaltered Public Function within a general module. Initially, I tried to simply use that in the "On Action" property like it was used in A2003, i.e., =DelReg("RegistryID"), but that fails also.

Public Function xfrDelReg(dummy As Integer)Dim lngRegID As Long
lngRegID = Forms("frmRegistry").ActiveControl!RegistryID
'lngRegID = Forms("frmRegistry").ActiveControl.Form.RegistryID
'lngRegID = Forms("frmRegistry").ActiveControl.Form("RegistryID")
'lngRegID = Forms("frmRegistry").ActiveControl.Form([RegistryID])
DelReg (lngRegID)
End Function

[GraeagleBill]

Yes, I've already done the call to the Public Function in a form's module successfully. It may be that I have to move the Public Function DelReg from the general module to the form's module, but that still leaves me lacking in the field value I need. I'll try that in the AM and see if the desired record still has the focus after the run around. It might prove a bit tricky, as function DelReg is sometimes operating on a clone RecordSource versus sometimes a query........ we'll see

[June7]

They all worked in test with my db. But I was not using a function. I tested in the Immediate Window.

[GraeagleBill]

The only way I've been able to find success is to move the Public Function DelReg code to the form's module, then route the "On Action" of the CommandBar through a Call to the DelReg function in the form's module. The amount of code in the DelReg function isn't particularly voluminous, so I guess it's a small price to pay to get the job done. The downside, IMHO, is I'll have to duplicate the code in another instance where the function is required.