If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
#Error
I'm re-designing my reports to be a little more clean. I'm using the trick
Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
#2
|
|||
|
|||
JohnLute wrote:
I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] The only reason I can think of for that si that the text box name is the same as the name of a field in the expression. If so, change the name of the text box to something else such as txtCaliperThickness+TOL -- Marsh MVP [MS Access] |
#3
|
|||
|
|||
What do you get if you change the name of the field/column in the query to
something like: CalThickMinusTOL: [CaliperThickness-TOL] I detest using any type of symbols in object names. I might allow an occasional underscore but certainly not "#$%-+*". Looks like I am cursing... -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
#4
|
|||
|
|||
Thanks, Duane.
I reviewed yours and Marshall's replies. I changed the name of the field/column to "MIN" and the field in the table to "CaliperThicknessMinTOL" I still get the #Error!!! What the #$%-+* is going on??? Any ideas? -- www.Marzetti.com "Duane Hookom" wrote: What do you get if you change the name of the field/column in the query to something like: CalThickMinusTOL: [CaliperThickness-TOL] I detest using any type of symbols in object names. I might allow an occasional underscore but certainly not "#$%-+*". Looks like I am cursing... -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
#5
|
|||
|
|||
"MIN" isn't a good name since it is an aggregate function. If you take the
time to name a control on a report, consider using a prefix like "txt". Sometimes #Error is a result of another calculation in the report section. -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message news Thanks, Duane. I reviewed yours and Marshall's replies. I changed the name of the field/column to "MIN" and the field in the table to "CaliperThicknessMinTOL" I still get the #Error!!! What the #$%-+* is going on??? Any ideas? -- www.Marzetti.com "Duane Hookom" wrote: What do you get if you change the name of the field/column in the query to something like: CalThickMinusTOL: [CaliperThickness-TOL] I detest using any type of symbols in object names. I might allow an occasional underscore but certainly not "#$%-+*". Looks like I am cursing... -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
#6
|
|||
|
|||
Please see my first response below. I went tinkering around and wondered if
the CaliperThicknessMinTOL It's data type is number with the field size set to double and the format fixed to 4 decimal places. Are these settings maybe fouling up things? Being a number data type is the only difference I see between what is and isn't working. -- www.Marzetti.com "Duane Hookom" wrote: What do you get if you change the name of the field/column in the query to something like: CalThickMinusTOL: [CaliperThickness-TOL] I detest using any type of symbols in object names. I might allow an occasional underscore but certainly not "#$%-+*". Looks like I am cursing... -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
#7
|
|||
|
|||
I changed the table field name to "CaliperThicknessMITOL"
The #Error persists! I'm not having this issue with any other field data types. I'm starting to conclude that it's due to the number data type of the field. -- www.Marzetti.com "Duane Hookom" wrote: "MIN" isn't a good name since it is an aggregate function. If you take the time to name a control on a report, consider using a prefix like "txt". Sometimes #Error is a result of another calculation in the report section. -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message news Thanks, Duane. I reviewed yours and Marshall's replies. I changed the name of the field/column to "MIN" and the field in the table to "CaliperThicknessMinTOL" I still get the #Error!!! What the #$%-+* is going on??? Any ideas? -- www.Marzetti.com "Duane Hookom" wrote: What do you get if you change the name of the field/column in the query to something like: CalThickMinusTOL: [CaliperThickness-TOL] I detest using any type of symbols in object names. I might allow an occasional underscore but certainly not "#$%-+*". Looks like I am cursing... -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
#8
|
|||
|
|||
I just confirmed that the error is due to the datat type of the field. I
changed it from number to text and the error went away. -- www.Marzetti.com "Duane Hookom" wrote: "MIN" isn't a good name since it is an aggregate function. If you take the time to name a control on a report, consider using a prefix like "txt". Sometimes #Error is a result of another calculation in the report section. -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message news Thanks, Duane. I reviewed yours and Marshall's replies. I changed the name of the field/column to "MIN" and the field in the table to "CaliperThicknessMinTOL" I still get the #Error!!! What the #$%-+* is going on??? Any ideas? -- www.Marzetti.com "Duane Hookom" wrote: What do you get if you change the name of the field/column in the query to something like: CalThickMinusTOL: [CaliperThickness-TOL] I detest using any type of symbols in object names. I might allow an occasional underscore but certainly not "#$%-+*". Looks like I am cursing... -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
#9
|
|||
|
|||
Sorry for the spasmodic posts.
So it looks like this doesn't work with fields of the number data type. Have you ever experienced thi before? Any ways around it? I'd hate to change the data types because I want to be able to fix all numerical values to 4 decimal points. Thanks! -- www.Marzetti.com "Duane Hookom" wrote: "MIN" isn't a good name since it is an aggregate function. If you take the time to name a control on a report, consider using a prefix like "txt". Sometimes #Error is a result of another calculation in the report section. -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message news Thanks, Duane. I reviewed yours and Marshall's replies. I changed the name of the field/column to "MIN" and the field in the table to "CaliperThicknessMinTOL" I still get the #Error!!! What the #$%-+* is going on??? Any ideas? -- www.Marzetti.com "Duane Hookom" wrote: What do you get if you change the name of the field/column in the query to something like: CalThickMinusTOL: [CaliperThickness-TOL] I detest using any type of symbols in object names. I might allow an occasional underscore but certainly not "#$%-+*". Looks like I am cursing... -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
#10
|
|||
|
|||
I wouldn't change the data type in the field. Try
="This is the Caption: " + IIf(IsNull([numericfield]), Null, "") -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... Sorry for the spasmodic posts. So it looks like this doesn't work with fields of the number data type. Have you ever experienced thi before? Any ways around it? I'd hate to change the data types because I want to be able to fix all numerical values to 4 decimal points. Thanks! -- www.Marzetti.com "Duane Hookom" wrote: "MIN" isn't a good name since it is an aggregate function. If you take the time to name a control on a report, consider using a prefix like "txt". Sometimes #Error is a result of another calculation in the report section. -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message news Thanks, Duane. I reviewed yours and Marshall's replies. I changed the name of the field/column to "MIN" and the field in the table to "CaliperThicknessMinTOL" I still get the #Error!!! What the #$%-+* is going on??? Any ideas? -- www.Marzetti.com "Duane Hookom" wrote: What do you get if you change the name of the field/column in the query to something like: CalThickMinusTOL: [CaliperThickness-TOL] I detest using any type of symbols in object names. I might allow an occasional underscore but certainly not "#$%-+*". Looks like I am cursing... -- Duane Hookom MS Access MVP -- "JohnLute" wrote in message ... I'm re-designing my reports to be a little more clean. I'm using the trick Duane Hookom suggested: convert labels to text boxes and use the control source to make them visible or invisible depending if they have a value or not. So far it's working as expected, however, I came upon a glitch. I have "-" and "+" tolerance values for many reported attributes. When applying the control source code the report returns a "#Error" that appears on the report for that control. Here's the control source: ="- "+[CaliperThickness-TOL] I'm assuming the "-" is causing fits. I have the same issue with: ="+ "+[CaliperThickness+TOL] Any way around this? Thanks in advance! -- www.Marzetti.com |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Reserved Error - 1104 - Works in 97 not in XP? | beveritt | General Discussion | 0 | August 25th, 2005 05:07 PM |
Error trapped only while stepping through the code - Not triggered when run | Jeff | General Discussion | 0 | February 28th, 2005 06:26 PM |
Error message different in MDB and MDE | david epsom dot com dot au | General Discussion | 1 | September 21st, 2004 12:47 AM |
Product Key for Office XP | P.G.Indiana | Setup, Installing & Configuration | 1 | June 7th, 2004 03:22 AM |
Error #1321 MOS 2003 Setup | Chad Harris | Setup, Installing & Configuration | 1 | June 7th, 2004 12:22 AM |