G
Guest
I am getting a strange error message in a couple of routines that I have in
my report. It says run time error 2427 and "You entered an expression that
has no value".
This is in the Report Open event and I tried putting it in the Report
Activate event because this occurs after Open.
I have an 'If' statement that checks the value of a textbox on the report.
The value shows on the report so it is there.
Whether the value is 5 or 7 determines which function to use to make a
calculation based on two other values in the report. Neither of these values
are available either if I put the 5 or 7 in to force the calculation.
I have other calculations ahead of these that work fine and are based on
hidden checkboxes where the the stored values -1 or 0 have to be displayed as
1, 0 or "" depending on certain conditions. These If's and calc's work great.
I'm sure there is a simple explanation but I can't figure out why these
three values aren't available to the VB routine and others in the same report
are. To make it even stranger it actually seemed to work a couple times
during troubleshooting but then wasn't permanent and never worked again.
my report. It says run time error 2427 and "You entered an expression that
has no value".
This is in the Report Open event and I tried putting it in the Report
Activate event because this occurs after Open.
I have an 'If' statement that checks the value of a textbox on the report.
The value shows on the report so it is there.
Whether the value is 5 or 7 determines which function to use to make a
calculation based on two other values in the report. Neither of these values
are available either if I put the 5 or 7 in to force the calculation.
I have other calculations ahead of these that work fine and are based on
hidden checkboxes where the the stored values -1 or 0 have to be displayed as
1, 0 or "" depending on certain conditions. These If's and calc's work great.
I'm sure there is a simple explanation but I can't figure out why these
three values aren't available to the VB routine and others in the same report
are. To make it even stranger it actually seemed to work a couple times
during troubleshooting but then wasn't permanent and never worked again.