What am I missing here

[MattLewis]

In the code below, when Form_BeforeInsert runs, it's not giving me the value that was set previously when Form_Open ran. Why not?

Option Explicit


Private m_InternalJobRef As Long


Private Sub Form_BeforeInsert(Cancel As Integer)
  MsgBox m_InternalJobRef
End Sub


Private Sub Form_Open(Cancel As Integer)
  If Not IsNull(OpenArgs) Then
    m_InternalJobRef = CLng(OpenArgs)
    MsgBox m_InternalJobRef
  End If
End Sub

Yes, I realize I could OpenArgs from within Form_BeforeInsert, but I'm just learning VBA programming, and I want to understand why on God's green Earth do so many things not work like they are supposed to.

[Micron]

I see no reason why it wouldn't work as written. When you say it doesn't give you the value, do you mean in the msgbox of the BeforeUpdate event or somewhere else, like in the immediate window? I tried to replicate your issue, but it works for me.

[Missinglinq]

Like Micron, I can't reproduce your problem, either, which makes me wonder if the problem lies in the command, from another Form, that opens this Form; could you post it?

Also, this code,using the Before_Insert event, presumably applies to a New Record, but I see no evidence of you going to a such...is the Form's Data Entry Property set to Yes?

Linq ;0)>

[MattLewis]

The message box that shows in Sub Form_BeforeInsert comes up with 0, even though the value is being set prior to that during Sub Form_Open.

[Micron]

The only other idea I have at present is to temporarily take off the Clng coercion and/or make the global a variant for testing.
EDIT: mistakenly referred to variable as global. Meant to refer to its scope as being at the module level.

[Missinglinq]

even though the value is being set prior to that during Sub Form_Open.

Once again...since neither Micron nor I can reproduce the problem...I suspect that what you think is 'setting the value' isn't, in fact, setting the value! Which I why I asked for your code being used to open the Form, presumably from another Form.

Linq ;0)>

[MattLewis]

Get over the OpenArgs part of this. That functionality is working. What's not working is when I set a variable in one sub, it's not sticking for later use by other subs.

[MattLewis]

**** it. I'll just use a TextBox on the form, set it to visible=no, and use that to store my string.

[Missinglinq]

Get over the OpenArgs part of this. That functionality is working. What's not working is when I set a variable in one sub, it's not sticking for later use by other subs.

This also works, as intended, when I run it!

[John_G]

Not sure if this is the issue or not, but try changing

Private m_InternalJobRef As Long
to
Dim m_InternalJobRef As Long

Also check that the variable m_InternalJobRef is not declared (as Private or Dim) in another procedure in the same module, which could easily cause the problem you are having.

[Micron]

A variable Dim'd without an explicit scope keyword is Private by default, so the two declarations are the same.
That would also mean that if declared that way in another module, it would be private to that module regardless of which of those two declarations was used.
Without being able to see the actual code that opens the other form I think there's not much more that we can do. As noted, it works for at least two of us. I tested as written in the first post, including using the BeforeUpdate event to get the value.