Yes, the doubleclick module causes some things to happen, and what I now want
to happen FIRST is that it captures the value I described from the subform
and puts it in the global variable.  

The global variable is defined in a separate "Globals" module so it's
accessible from anywhere, not just from the subform-associated code.

I've experimented with several different variations of the
Forms!MainForm!subForm1.Forms.Controls "name-ology," adding or taking out
various pieces to try to find the right object string, but haven't hit on the
right one yet.  As I said, the closest I've come does indeed capture a value
and place it into the global variable, but it's Value1 from the FIRST record
in the subform, not from the record where the double-click action happened.