Re: Very vague error message
Yeah the whole page is basically a cfscript tag :) Ill have another look at it later, I do have some switch + case statements, ill ensure the syntax is correct and get back to you all. Thanks for all the replies :) On 17/11/03 3:17 am, Michael S. Hodgdon [EMAIL PROTECTED] wrote: I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
1000+ lines of code in a single CF template seems a bit excessive for starters. That depends on several things For all we know it could be 500 lines of code and 500 lines of remarks and spacing I've seen some templates which have about 300 lines of code, but the whole template is over 1,200 lines total... I tend to be space heavy on my code for readability, does that mean it's excessive? [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Very vague error message
Ok, tracked it down to the switch statement:
switch(type)
{
case request.AUTH_ACL:
result = u_access[j][key];
case request.AUTH_MOD:
result = result OR u_access[j]['auth_mod'];
case request.AUTH_ADMIN:
result = result OR is_admin;
break;
}
On reading the cf reference I see that in a switch statement:
³Each constant value must be a constant (that is, not a variable, a
function, or other _expression_).²
As you can see each of my case¹s is a variable which is the problem... Is
there any way of using the variable but not getting the error?
On 17/11/03 3:17 am, Michael S. Hodgdon [EMAIL PROTECTED]
wrote:
I have never come across this in a ColdFusion.One way you can try to
pinpoint the error is to place cfabort statement at say, line 50. Run your
code and if you don't get an error, place the cfabort on line 100 and run
the code.Keep doing this until you get closer to the error.
Do you have any idea where it could be?It sounds as though ColdFusion is
saying do not place a dynamic variable in this evaluating statement.I
can't think of a place where this would be so.Are you using cfscript in
this page anywhere?If so, if you are using a case statement that reads
case constant, this may be the culprit.
Hope that helps.
-Original Message-
From: Ryan Mitchell [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 16, 2003 10:41 AM
To: CF-Talk
Subject: Very vague error message
Hello
I have a rather large page of code which ive been working on, and I get
the
following error:
This _expression_ must have a constant value.
It doesn¹t give me a line number, or a code snippet, just that text.
As I said I have a lot of code (1000+ lines) and I cant quite tie down the
problem... Has anyone come across this before?
Thanks,
Ryan
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
RE: Very vague error message
if(type IS request.AUTH_ACL){
result = u_access[j][key] OR u_access[j]['auth_mod'] OR is_admin;
}
else if(type IS request.AUTH_MOD){
result = result OR u_access[j]['auth_mod'] OR is_admin;
}
else if(type IS request.AUTH_ADMIN){
result = result OR is_admin;
}
-Original Message-
From: Ryan Mitchell [mailto:[EMAIL PROTECTED]
Sent: maandag 17 november 2003 13:07
To: CF-Talk
Subject: Re: Very vague error message
Ok, tracked it down to the switch statement:
switch(type)
{
case request.AUTH_ACL:
result = u_access[j][key];
case request.AUTH_MOD:
result = result OR u_access[j]['auth_mod'];
case request.AUTH_ADMIN:
result = result OR is_admin;
break;
}
On reading the cf reference I see that in a switch statement:
³Each constant value must be a constant (that is, not a variable, a
function, or other _expression_).²
As you can see each of my case¹s is a variable which is the problem... Is
there any way of using the variable but not getting the error?
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
RE: Very vague error message
if()
Oh, and you forgot the break; in the first 2 case statements
-Original Message-
From: Ryan Mitchell [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2003 7:07 AM
To: CF-Talk
Subject: Re: Very vague error message
Ok, tracked it down to the switch statement:
switch(type)
{
case request.AUTH_ACL:
result = u_access[j][key];
case request.AUTH_MOD:
result = result OR u_access[j]['auth_mod'];
case request.AUTH_ADMIN:
result = result OR is_admin;
break;
}
On reading the cf reference I see that in a switch statement:
³Each constant value must be a constant (that is, not a variable, a
function, or other _expression_).²
As you can see each of my case¹s is a variable which is the problem...
Is
there any way of using the variable but not getting the error?
On 17/11/03 3:17 am, Michael S. Hodgdon [EMAIL PROTECTED]
wrote:
I have never come across this in a ColdFusion.One way you can try to
pinpoint the error is to place cfabort statement at say, line 50.
Run your
code and if you don't get an error, place the cfabort on line 100
and run
the code.Keep doing this until you get closer to the error.
Do you have any idea where it could be?It sounds as though
ColdFusion is
saying do not place a dynamic variable in this evaluating statement.
I
can't think of a place where this would be so.Are you using
cfscript in
this page anywhere?If so, if you are using a case statement that
reads
case constant, this may be the culprit.
Hope that helps.
-Original Message-
From: Ryan Mitchell [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 16, 2003 10:41 AM
To: CF-Talk
Subject: Very vague error message
Hello
I have a rather large page of code which ive been working on, and I
get
the
following error:
This _expression_ must have a constant value.
It doesn¹t give me a line number, or a code snippet, just that text.
As I said I have a lot of code (1000+ lines) and I cant quite tie
down the
problem... Has anyone come across this before?
Thanks,
Ryan
_
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
RE: Very vague error message
Looking at his code, I think it was intentional -Original Message- From: Philip Arnold [mailto:[EMAIL PROTECTED] Sent: maandag 17 november 2003 13:21 To: CF-Talk Subject: RE: Very vague error message if() Oh, and you forgot the break; in the first 2 case statements [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Very vague error message
Lol, should have thought of that, I was just thinking there was a clever
solution :)
On 17/11/03 12:20 pm, Pascal Peters [EMAIL PROTECTED] wrote:
if(type IS request.AUTH_ACL){
result = u_access[j][key] OR u_access[j]['auth_mod'] OR is_admin;
}
else if(type IS request.AUTH_MOD){
result = result OR u_access[j]['auth_mod'] OR is_admin;
}
else if(type IS request.AUTH_ADMIN){
result = result OR is_admin;
}
-Original Message-
From: Ryan Mitchell [mailto:[EMAIL PROTECTED]
Sent: maandag 17 november 2003 13:07
To: CF-Talk
Subject: Re: Very vague error message
Ok, tracked it down to the switch statement:
switch(type)
{
case request.AUTH_ACL:
result = u_access[j][key];
case request.AUTH_MOD:
result = result OR u_access[j]['auth_mod'];
case request.AUTH_ADMIN:
result = result OR is_admin;
break;
}
On reading the cf reference I see that in a switch statement:
³Each constant value must be a constant (that is, not a variable, a
function, or other _expression_).²
As you can see each of my case¹s is a variable which is the problem... Is
there any way of using the variable but not getting the error?
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
RE: Very vague error message
But, without the break; in the case, this doesn't do the same thing
If you want to do EXACTLY what the switch did, then you don't want the
else if, but just if
-Original Message-
From: Pascal Peters [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2003 7:20 AM
To: CF-Talk
Subject: RE: Very vague error message
if(type IS request.AUTH_ACL){
result = u_access[j][key] OR u_access[j]['auth_mod'] OR is_admin;
}
else if(type IS request.AUTH_MOD){
result = result OR u_access[j]['auth_mod'] OR is_admin;
}
else if(type IS request.AUTH_ADMIN){
result = result OR is_admin;
}
-Original Message-
From: Ryan Mitchell [mailto:[EMAIL PROTECTED]
Sent: maandag 17 november 2003 13:07
To: CF-Talk
Subject: Re: Very vague error message
Ok, tracked it down to the switch statement:
switch(type)
{
case request.AUTH_ACL:
result = u_access[j][key];
case request.AUTH_MOD:
result = result OR u_access[j]['auth_mod'];
case request.AUTH_ADMIN:
result = result OR is_admin;
break;
}
On reading the cf reference I see that in a switch statement:
³Each constant value must be a constant (that is, not a variable, a
function, or other _expression_).²
As you can see each of my case¹s is a variable which is the problem...
Is
there any way of using the variable but not getting the error?
_
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
RE: Very vague error message
If you examine my code, you see I changed the code to set result. In any case, it can't do EXACTLY what the switch did, because the switch did nothing. I suppose you can do it with if's too (if that is what he wants to do) and probably the code will even be better then.
-Original Message-
From: Philip Arnold [mailto:[EMAIL PROTECTED]
Sent: maandag 17 november 2003 14:40
To: CF-Talk
Subject: RE: Very vague error message
But, without the break; in the case, this doesn't do the same thing
If you want to do EXACTLY what the switch did, then you don't want the
else if, but just if
-Original Message-
From: Pascal Peters [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2003 7:20 AM
To: CF-Talk
Subject: RE: Very vague error message
if(type IS request.AUTH_ACL){
result = u_access[j][key] OR u_access[j]['auth_mod'] OR is_admin;
}
else if(type IS request.AUTH_MOD){
result = result OR u_access[j]['auth_mod'] OR is_admin;
}
else if(type IS request.AUTH_ADMIN){
result = result OR is_admin;
}
-Original Message-
From: Ryan Mitchell [mailto:[EMAIL PROTECTED]
Sent: maandag 17 november 2003 13:07
To: CF-Talk
Subject: Re: Very vague error message
Ok, tracked it down to the switch statement:
switch(type)
{
case request.AUTH_ACL:
result = u_access[j][key];
case request.AUTH_MOD:
result = result OR u_access[j]['auth_mod'];
case request.AUTH_ADMIN:
result = result OR is_admin;
break;
}
On reading the cf reference I see that in a switch statement:
³Each constant value must be a constant (that is, not a variable, a
function, or other _expression_).²
As you can see each of my case¹s is a variable which is the problem...
Is
there any way of using the variable but not getting the error?
_
_
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
Very vague error message
Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
i always use Im here (#timeFormat(now(),'hh:mm:ss')# ! cfabort and place it before trouble points, or after them to see if they are really, trouble points.stepping through the code, its the easiest way i can see for myself to debug, unless i know *exactly* where the code is wrong, of course. but, you probably already use something like this... :) and funny enough, the message Im here is usually a gauge of frustration with the particular problem, lots of times it has some four letter words mixed in, cursing that damn jeremy allaire for creating this cursed thing we all LOVE, cf. tony -Original Message- From: Michael S. Hodgdon [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:18 PM To: CF-Talk Subject: RE: Very vague error message I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
assuming that it is within cfoutput/cfoutput tags, that is ;) tony -Original Message- From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:24 PM To: CF-Talk Subject: RE: Very vague error message i always use Im here (#timeFormat(now(),'hh:mm:ss')# ! cfabort and place it before trouble points, or after them to see if they are really, trouble points.stepping through the code, its the easiest way i can see for myself to debug, unless i know *exactly* where the code is wrong, of course. but, you probably already use something like this... :) and funny enough, the message Im here is usually a gauge of frustration with the particular problem, lots of times it has some four letter words mixed in, cursing that damn jeremy allaire for creating this cursed thing we all LOVE, cf. tony -Original Message- From: Michael S. Hodgdon [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:18 PM To: CF-Talk Subject: RE: Very vague error message I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
How about cftrace? _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:24 PM To: CF-Talk Subject: RE: Very vague error message i always use Im here (#timeFormat(now(),'hh:mm:ss')# ! cfabort and place it before trouble points, or after them to see if they are really, trouble points.stepping through the code, its the easiest way i can see for myself to debug, unless i know *exactly* where the code is wrong, of course. but, you probably already use something like this... :) and funny enough, the message Im here is usually a gauge of frustration with the particular problem, lots of times it has some four letter words mixed in, cursing that damn jeremy allaire for creating this cursed thing we all LOVE, cf. tony -Original Message- From: Michael S. Hodgdon [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:18 PM To: CF-Talk Subject: RE: Very vague error message I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
how about it? never used it :) tw -Original Message- From: Michael T. Tangorre [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:33 PM To: CF-Talk Subject: RE: Very vague error message How about cftrace? _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:24 PM To: CF-Talk Subject: RE: Very vague error message i always use Im here (#timeFormat(now(),'hh:mm:ss')# ! cfabort and place it before trouble points, or after them to see if they are really, trouble points.stepping through the code, its the easiest way i can see for myself to debug, unless i know *exactly* where the code is wrong, of course. but, you probably already use something like this... :) and funny enough, the message Im here is usually a gauge of frustration with the particular problem, lots of times it has some four letter words mixed in, cursing that damn jeremy allaire for creating this cursed thing we all LOVE, cf. tony -Original Message- From: Michael S. Hodgdon [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:18 PM To: CF-Talk Subject: RE: Very vague error message I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
Weegs, how did the test go? _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:37 PM To: CF-Talk Subject: RE: Very vague error message how about it? never used it :) tw -Original Message- From: Michael T. Tangorre [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:33 PM To: CF-Talk Subject: RE: Very vague error message How about cftrace? _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:24 PM To: CF-Talk Subject: RE: Very vague error message i always use Im here (#timeFormat(now(),'hh:mm:ss')# ! cfabort and place it before trouble points, or after them to see if they are really, trouble points.stepping through the code, its the easiest way i can see for myself to debug, unless i know *exactly* where the code is wrong, of course. but, you probably already use something like this... :) and funny enough, the message Im here is usually a gauge of frustration with the particular problem, lots of times it has some four letter words mixed in, cursing that damn jeremy allaire for creating this cursed thing we all LOVE, cf. tony -Original Message- From: Michael S. Hodgdon [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:18 PM To: CF-Talk Subject: RE: Very vague error message I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan _ _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
taking it @ max on the 20th :) studying while working tonight!! tw -Original Message- From: Michael T. Tangorre [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:42 PM To: CF-Talk Subject: RE: Very vague error message Weegs, how did the test go? _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:37 PM To: CF-Talk Subject: RE: Very vague error message how about it? never used it :) tw -Original Message- From: Michael T. Tangorre [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:33 PM To: CF-Talk Subject: RE: Very vague error message How about cftrace? _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:24 PM To: CF-Talk Subject: RE: Very vague error message i always use Im here (#timeFormat(now(),'hh:mm:ss')# ! cfabort and place it before trouble points, or after them to see if they are really, trouble points.stepping through the code, its the easiest way i can see for myself to debug, unless i know *exactly* where the code is wrong, of course. but, you probably already use something like this... :) and funny enough, the message Im here is usually a gauge of frustration with the particular problem, lots of times it has some four letter words mixed in, cursing that damn jeremy allaire for creating this cursed thing we all LOVE, cf. tony -Original Message- From: Michael S. Hodgdon [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:18 PM To: CF-Talk Subject: RE: Very vague error message I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan _ _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
Cool. I wish I wasn't up Managerial accounting homework is not as much fun as Cold Fusion Coding :-) _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:42 PM To: CF-Talk Subject: RE: Very vague error message taking it @ max on the 20th :) studying while working tonight!! tw -Original Message- From: Michael T. Tangorre [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:42 PM To: CF-Talk Subject: RE: Very vague error message Weegs, how did the test go? _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:37 PM To: CF-Talk Subject: RE: Very vague error message how about it? never used it :) tw -Original Message- From: Michael T. Tangorre [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:33 PM To: CF-Talk Subject: RE: Very vague error message How about cftrace? _ From: Tony Weeg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:24 PM To: CF-Talk Subject: RE: Very vague error message i always use Im here (#timeFormat(now(),'hh:mm:ss')# ! cfabort and place it before trouble points, or after them to see if they are really, trouble points.stepping through the code, its the easiest way i can see for myself to debug, unless i know *exactly* where the code is wrong, of course. but, you probably already use something like this... :) and funny enough, the message Im here is usually a gauge of frustration with the particular problem, lots of times it has some four letter words mixed in, cursing that damn jeremy allaire for creating this cursed thing we all LOVE, cf. tony -Original Message- From: Michael S. Hodgdon [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:18 PM To: CF-Talk Subject: RE: Very vague error message I have never come across this in a ColdFusion.One way you can try to pinpoint the error is to place cfabort statement at say, line 50. Run your code and if you don't get an error, place the cfabort on line 100 and run the code.Keep doing this until you get closer to the error. Do you have any idea where it could be?It sounds as though ColdFusion is saying do not place a dynamic variable in this evaluating statement.I can't think of a place where this would be so.Are you using cfscript in this page anywhere?If so, if you are using a case statement that reads case constant, this may be the culprit. Hope that helps. -Original Message- From: Ryan Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, November 16, 2003 10:41 AM To: CF-Talk Subject: Very vague error message Hello I have a rather large page of code which ive been working on, and I get the following error: This _expression_ must have a constant value. It doesn¹t give me a line number, or a code snippet, just that text. As I said I have a lot of code (1000+ lines) and I cant quite tie down the problem... Has anyone come across this before? Thanks, Ryan _ _ _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Very vague error message
1000+ lines of code in a single CF template seems a bit excessive for starters. Peter Tilbrook Transitional Services - Enterprise eSolutions Centrelink (http://www.centrelink.gov.au) 2 Faulding Street Symonston ACT 2609 Tel: (02) 62115927 Michael S. HodgdonTo: CF-Talk [EMAIL PROTECTED] [EMAIL PROTECTED]cc: omcast.netSubject:RE: Very vague error message 17/11/2003 14:17 Please respond to | [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
