Solved

Check for input in optional form variable

Posted on 2014-03-05
11
268 Views
Last Modified: 2014-03-05
I have a function with some arguments, and one of them is optional and of the "form" variable type.

Public Function MyFunction(Argument1 as Boolean, Optional TheForm as Form) as String
    If TheForm is null Then
        'Do something
    End If
End Function

"TheForm is null" always returns false, whether or not anything has been entered for that argument.
Is there an explicit way the to test whether something was entered for TheForm argument, without using error trapping, or using a variant variable type?  That should be possible, right??
0
Comment
Question by:Jolio81
  • 5
  • 3
  • 2
  • +1
11 Comments
 
LVL 35

Expert Comment

by:PatHartman
ID: 39906869
Try using IsEmpty() when referring to an object.
0
 

Author Comment

by:Jolio81
ID: 39906921
Public Function MyFunction(Argument1 As Boolean, Optional TheForm As Form) As String
    MyFunction = "Is TheForm Empty? " & IsEmpty(TheForm)
End Function

In the Immediate window, I type:
debug.print myfunction(True)

The result I get is this:
Is TheForm Empty? False
0
 
LVL 47

Expert Comment

by:Dale Fye (Access MVP)
ID: 39906959
Try IsMissing()  or Is Nothing

Public Function MyFunction(Arguement1 as boolean, Optional TheForm as Form) as String

MyFunction = "Is TheForm Missing:  " & isMissing(TheForm) & vbcrlf _
                     & "Is TheForm Nothing: " & (TheForm is nothing)

End function

I think you will find, that the Is Nothing syntax is what you are looking for.
0
Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

 
LVL 30

Accepted Solution

by:
hnasr earned 450 total points
ID: 39907099
Try:
Public Function MyFunction(Argument1 As Boolean, Optional TheForm As Form) As String
    If TypeName(TheForm) = "Nothing" Then
        'Do something
        MsgBox ("Optioanal argument ignored")
    End If
End Function

Open in new window

0
 

Author Comment

by:Jolio81
ID: 39907377
Fyed,

I tried this:

Public Function MyFunction(Argument1 As Boolean, Optional TheForm As Form) As String
    MyFunction = "Is TheForm nothing? " & TheForm Is Nothing
End Function

but it threw "Compile error: Type mismatch".  I also tried "TheForm = Nothing" but got the same.

IsMissing didn't work either; the function returned "Is TheForm missing? false"
0
 

Author Closing Comment

by:Jolio81
ID: 39907393
Works great!  Thanks hnasr!
0
 
LVL 47

Expert Comment

by:Dale Fye (Access MVP)
ID: 39907410
Well, if you had included the parenthesis around the expression, as I did in my example, it would have worked properly.

MyFunction = "Is TheForm Nothing: " & (TheForm is nothing)

When you left out the parenthesis, Access assumed you wanted to contatenate the TheForm (which "is nothing" as it was not passed to the function) to the text "Is TheForm Nothing", which is why you got a type missmatch.  By including the parenthesis, you force evaluation of the Is Nothing test and then concatenate either True or False to the string.
0
 
LVL 30

Expert Comment

by:hnasr
ID: 39907420
Welcome!
0
 

Author Comment

by:Jolio81
ID: 39907543
Dear Fyed,

Let us blame those at Microsoft for the willy-nilly behavior of the compiler.  The following does work properly without parentheses:

      debug.Print "Does not true = false? " & not true = false

and yet

      "Is TheForm nothing? " & TheForm Is Nothing

does not.  I think that's dumb.  Sorry, I would have definitely given you points.
0
 
LVL 47

Expert Comment

by:Dale Fye (Access MVP)
ID: 39907726
@jolio81

you have to set some form of precedence when doing evaluation, what's the old adage

Parentheses, exponentiation, multiplication, division, addition, subtraction

in the case above, I'm sure the "=" and "Not" operators have priority over the "&"

doesn't appear that "xxxxx is Nothing" is higher in priority than "&", which is why I generally explicitly wrap this type of thing in parentheses.

No prob on the points, the point in my explanation was to help you understand the behavior.
0
 

Author Comment

by:Jolio81
ID: 39907810
I appreciate the advice; I'll start making a habit of using parentheses.  Thanks Fyed!
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you are entering numbers in a speadsheet, and don't remember what 6×7 is, you just type “=6*7" instead. It works in every cell! This is not so in Access. To enter the elusive 42 in a text box, you have to find a calculator, and then copy the re…
In a multiple monitor setup, if you don't want to use AutoCenter to position your popup forms, you have a problem: where will they appear?  Sometimes you may have an additional problem: where the devil did they go?  If you last had a popup form open…
Basics of query design. Shows you how to construct a simple query by adding tables, perform joins, defining output columns, perform sorting, and apply criteria.
What’s inside an Access Desktop Database. Will look at the basic interface, Navigation Pane (Database Container), Tables, Queries, Forms, Report, Macro’s, and VBA code.

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question