Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!
COURSE of the MONTH
10 days, 15 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
ms access #TYPE! error on report when no data
Posted on 2016-08-26
Hello-
I have an MS access report. Run perfect when where is data. If there is NO data I get a #Type! error on a particular field
In the report itself, under the detail section I have a text box that contains a TRIM statement: =Trim([PRIMARY_NAME]) & " " & Trim([Label_NAME])
If there is no data on the report, I get #Type! error showing on the report when I run the print preview.
I tried to modify the trim statement to be : =IIf(IsNull([PRIMARY_NAME]
I wrote it so if the PRIMARY_NAME field was null then it would just output a blank space. This was probably wrong because there is 2 fields in my trim statement.
I am probably missing something simple.... can someone give advice how to get rid of that #Type! error? Thank you.
I have an MS access report. Run perfect when where is data. If there is NO data I get a #Type! error on a particular field
In the report itself, under the detail section I have a text box that contains a TRIM statement: =Trim([PRIMARY_NAME]) & " " & Trim([Label_NAME])
If there is no data on the report, I get #Type! error showing on the report when I run the print preview.
I tried to modify the trim statement to be : =IIf(IsNull([PRIMARY_NAME]
I wrote it so if the PRIMARY_NAME field was null then it would just output a blank space. This was probably wrong because there is 2 fields in my trim statement.
I am probably missing something simple.... can someone give advice how to get rid of that #Type! error? Thank you.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
2
4 Comments
IsNull vs Nz()
IsNull returns a Boolean, true or false
Nz(TheNullItem, TheSubstitute) substitutes something for the null.
Why are you TRIMing?
You should take care of that earlier.
Here's a fun trick.
In the query create two computed fields
tPRIMARY_NAME:Trim(PRIMARY
tLabel_NAME: Trim(LABEL_NAME)
Make your control
=[tPRIMARY_NAME] + " " + [tLabel_NAME]
Only in Access controls does the + concatenation propogate null.
You'll only get the text of the Primary name, the text of the Label name, or both with a space in between.
IsNull returns a Boolean, true or false
Nz(TheNullItem, TheSubstitute) substitutes something for the null.
Why are you TRIMing?
You should take care of that earlier.
Here's a fun trick.
In the query create two computed fields
tPRIMARY_NAME:Trim(PRIMARY
tLabel_NAME: Trim(LABEL_NAME)
Make your control
=[tPRIMARY_NAME] + " " + [tLabel_NAME]
Only in Access controls does the + concatenation propogate null.
You'll only get the text of the Primary name, the text of the Label name, or both with a space in between.
I was/am concatenating the 2 fields. I could put them together in the query.
Just wondering if there was a way to do this in the report.
Just wondering if there was a way to do this in the report.
Active today
The problem with an empty recordset is that you don't even get a NULL, but #Error.
Paste the following code into a standard module:
Function AvoidError(n As Variant, varReplaceWith As Variant)
10 On Error GoTo AvoidError_Error
20 AvoidError = Nz(n, varReplaceWith)
AvoidError_Exit:
30 Exit Function
AvoidError_Error:
40 AvoidError = varReplaceWith
50 Resume AvoidError_Exit
End Function
and make sure you call the module something other then AvoidError if it's a new module. Then make your control source:
=AvoidError(Trim([PRIMARY_
This doesn't always work in all cases though. Microsoft built in some optimizations that defeat this in some cases. So sometimes you need to break it up in to two steps; A hidden control with your expression, then a visible control with =AvoidError(<visible control>).
The other way to do this is to either check the recordcount in your IIF statement or hasdata and if no records, display a blank (this is looking at a subreport):
IIf(me.rptMonthlyStatCo.re
I find AvoidError() easier to use and it works most of the time without issue.
Jim.
Paste the following code into a standard module:
Function AvoidError(n As Variant, varReplaceWith As Variant)
10 On Error GoTo AvoidError_Error
20 AvoidError = Nz(n, varReplaceWith)
AvoidError_Exit:
30 Exit Function
AvoidError_Error:
40 AvoidError = varReplaceWith
50 Resume AvoidError_Exit
End Function
and make sure you call the module something other then AvoidError if it's a new module. Then make your control source:
=AvoidError(Trim([PRIMARY_
This doesn't always work in all cases though. Microsoft built in some optimizations that defeat this in some cases. So sometimes you need to break it up in to two steps; A hidden control with your expression, then a visible control with =AvoidError(<visible control>).
The other way to do this is to either check the recordcount in your IIF statement or hasdata and if no records, display a blank (this is looking at a subreport):
IIf(me.rptMonthlyStatCo.re
I find AvoidError() easier to use and it works most of the time without issue.
Jim.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article describes a method of delivering Word templates for use in merging Access data to Word documents, that requires no computer knowledge on the part of the recipient -- the templates are saved in table fields, and are extracted and install…
Traditionally, the method to display pictures in Access forms and reports is to first download them from URLs to a folder, record the path in a table and then let the form or report pull the pictures from that folder.
But why not let Windows retr…
Learn how to number pages in an Access report over each group.
Activate two pass printing by referencing the pages property:
Add code to the Page Footers OnFormat event to capture the pages as there occur for each group. Use the pages property to …
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
Suggested Courses
Course of the Month10 days, 15 hours left to enroll
770 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.