views:

1294

answers:

5

I am using the OpenArgs parameter to send a value when using DoCmd.OpenForm:

`DoCmd.OpenForm "frmSetOther", acNormal, , , acFormAdd, acDialog, "value"`

I then use Me.OpenArgs inside the opened form to grab the value. It sometimes sends a Null value instead of the original string. What is wrong?

A: 

Is the value taken from a user completed control? Do you ensure that the focus is moved from the control before you run the openform line?

EDIT: The value property of the control will be equal to the previous value, which may be null, unless you do this.

Remou
A: 

I think I found the answer to my problem:

In my experience, OpenArgs has to be handled immediately upon opening of the form. (link)

I checked this by putting a break before attempting to use the OpenArgs value, and it was null. But when I remove the break, the program shows no error. This must only happen while developing.

lamcro
"OpenArgs has to be handled immediately upon opening of the form" I have *never* found this to be true and I frequently use OpenArgs.
Remou
I agree 100% with Remou
DJ
What do you do then, Remou?
lamcro
The OpenArgs argument is persistent throughout the life of the form instance.
David-W-Fenton
A: 

A very interesting alternative to this "openArgs" argument is to use the .properties collection of the currentProject.allforms("myFormName") object. When you need to pass a value to a form (such as a filter inherited from another control or another form, for example), just add the corresponding property for your form, and add your value to this property.

Example:

addPropertyToForm "formFilter","Tbl_myTable.myField LIKE 'A*'",myFormName

The called function will try to update the value of the "formFilter" property of the object. If the property does not exist (err 2455 is raised), it will be added as a new property in the error management code.

Function addPropertyToForm(_ 
    x_propertyName as string, _
    x_value As Variant, _
    x_formName As String) 
As Boolean

On Error GoTo errManager
CurrentProject.AllForms(x_formName).Properties(x_propertyName).Value = x_value
addPropertyToForm = True
On Error GoTo 0

Exit Function

errManager:
If Err.Number = 2455 Then
    CurrentProject.AllForms(x_formName).Properties.Add x_propertyName, Nz(x_value)
    Resume Next
Else
    msgbox err.number & ". The property " & x_propertyName & "was not created"
End If

End Function
Philippe Grondier
+3  A: 

Hi,

This often happens during developpment whem the form is already oppened (in edit mode for example) and you invoke the docmd.OpenForm function. In this case, the form is placed in normal (view) mode and the OnOpen and OnLoad events are raised, but the OpenArgs property is set to null no mater what you passed to docmd.OpenForm.

The solution is obviously to close the form before you invoke it with docmd.OpenForm. However there is a workaround I like to use. In the OnOpen event I check if me.OpenArgs is null and if it is I replace it with some debug values.

if not isnull(me.OpenArgs) then
   myvalue = me.OpenArgs
else
   msgbox "Debug mode"
   myValue = "foo"
endif
Mathieu Pagé
A: 

Answer here. your form may be already open, even in Design mode: http://www.tech-archive.net/Archive/Access/microsoft.public.access.formscoding/2007-02/msg00928.html