[AccessD] Sporadic "#ERROR" in Access 2007 Report Group Header

Brad Marks BradM at blackforestltd.com
Wed Mar 21 17:09:08 CDT 2012


Lambert and Stuart,

Thanks for your insights.

I may do some more experimenting when time permits.  It could be a
problem will nulls... not sure.  I believe that I was pulling the same
data each time, but I could be wrong.

I was almost hoping that someone would say that it is not a good idea to
use "IIF" or "SWITCH" in Report headers.

Thanks again,
Brad  



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart
McLachlan
Sent: Wednesday, March 21, 2012 4:59 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Sporadic "#ERROR" in Access 2007 Report Group
Header

Thatis my immediate thought too.

On 21 Mar 2012 at 15:10, Heenan, Lambert wrote:

> Absent any other information, I would be wondering about Null values
in the "group on" field.
> 
> Lambert 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks
> Sent: Wednesday, March 21, 2012 2:58 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Sporadic "#ERROR" in Access 2007 Report Group
Header
> 
> All, 
> 
> I ran into something that I am curious about.
> 
> I have a new report that has a header for one of the report groups.
> 
> I need to put information in the header that is derived from the field
that is being used for the "group on".
> 
> This field is a code such as "A" "B" "C".  I was using a SWITCH
command to change these codes into more meaningful words for the group
header.  
> 
> "A" = "Gold"
> "B" = "Silver"
> "C" = "Bronze"
> 
> In my testing, I would occasionally receive an "#ERROR" message.  Not
every time, just once in a while.
> 
> I then started to use an "IIF" instead of the switch command.  Again,
I would occasionally receive the "#ERROR".
> 
> Sporadic problems have always scared me.
> 
> As a result, I changed my approach and used an "IIF" in the underlying
query instead of using it in building the header field.  This seems to
work nicely.
> 
> Nevertheless, I am still curious as to why I was receiving the
sporadic errors earlier.
> 
> You feedback/insights would be most appreciated.
> 
> Thanks,
> Brad
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




More information about the AccessD mailing list