#Error
in [Reports]
|
From: JohnLute on 17 Aug 2005 17:39 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
From: Marshall Barton on 17 Aug 2005 19:09 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]
From: Duane Hookom on 17 Aug 2005 19:09 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" <JohnLute(a)discussions.microsoft.com> wrote in message news:EBF8EB0C-43C9-40AB-96C1-A2CF0C25D117(a)microsoft.com... > 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
From: JohnLute on 18 Aug 2005 11:51 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" <JohnLute(a)discussions.microsoft.com> wrote in message > news:EBF8EB0C-43C9-40AB-96C1-A2CF0C25D117(a)microsoft.com... > > 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 > > >
From: Duane Hookom on 18 Aug 2005 12:02 "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" <JohnLute(a)discussions.microsoft.com> wrote in message news:D2D40941-B68B-4675-A662-56E9D1F584C1(a)microsoft.com... > 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" <JohnLute(a)discussions.microsoft.com> wrote in message >> news:EBF8EB0C-43C9-40AB-96C1-A2CF0C25D117(a)microsoft.com... >> > 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 >> >> >>
|
Next
|
Last
Pages: 1 2 3 4 Prev: Choose printer+parameters programatically Next: Calculating negative and positive numbers |