I have a page with SQLView Pro that uses some LOGIC tokens. the page works fine for most parameter values that it is 'fed' however there is one instance where it throws up the following error. I cannot decipher from it what I need to do to fix the apparent error (Unexpected token "/"). Any ideas?

DotNetNuke.Services.Exceptions.ModuleLoadException: SyntaxError: Unexpected token "/"; expected one of "NOT", "-", , , , "True", "False", , , "null", , , "(", , "if", or "cast" Line: 1, Column: 1 ---> Ciloci.Flee.ExpressionCompileException: SyntaxError: Unexpected token "/"; expected one of "NOT", "-", , , , "True", "False", , , "null", , , "(", , "if", or "cast" Line: 1, Column: 1 ---> Ciloci.Flee.PerCederberg.Grammatica.Runtime.ParserLogException: Unexpected token "/"; expected one of "NOT", "-", , , , "True", "False", , , "null", , , "(", , "if", or "cast" Line: 1, Column: 1 at Ciloci.Flee.PerCederberg.Grammatica.Runtime.Parser.Parse() at Ciloci.Flee.ExpressionContext.DoParse() --- End of inner exception stack trace --- at Ciloci.Flee.ExpressionContext.DoParse() at Ciloci.Flee.ExpressionContext.Parse(String expression, IServiceProvider services) at Ciloci.Flee.Expression`1.Compile(String expression, ExpressionOptions options) at Ciloci.Flee.Expression`1..ctor(String expression, ExpressionContext context, Boolean isGeneric) at Ciloci.Flee.ExpressionContext.CompileGeneric[TResultType](String expression) at DNNStuff.Utilities.Expression.ExpressionHelpers.EvalulateExpression(String expression) at DNNStuff.Utilities.RegularExpression.DataRowMatch.MatchHandler(Match m) at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator) at DNNStuff.Utilities.RegularExpression.DataRowMatch.Replace(String text) at DNNStuff.Utilities.RegularExpression.DataRowMatch.MatchHandler(Match m) at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator) at DNNStuff.Utilities.RegularExpression.DataRowMatch.Replace(String text) at DNNStuff.Utilities.RegularExpression.DataSetTokenReplacement.MatchHandler(Match m) at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator) at DNNStuff.Utilities.RegularExpression.DataSetTokenReplacement.Replace(String text) at DNNStuff.SQLViewPro.TokenReplacement.ReplaceTokens(String text, Hashtable settings, DataSet ds) at DNNStuff.SQLViewPro.Controls.ReportControlBase.ReplaceTokens(String text, DataSet ds) at DNNStuff.SQLViewPro.StandardReports.TemplateReportControl.BindTemplate() at DNNStuff.SQLViewPro.StandardReports.TemplateReportControl.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

Hi Eoghan,

I can't tell from that error either. Can you send the template snippet you think might be causing the trouble.

Thanks Richard for the quick reply.

Actually, when I look into the template what I see in terms of Logic token is very straightforward (e.g. [IFNOTMSURL VALUE=""] [/IFNOTMSURL]) so I now doubt that it is that.

I am wondering could it be related to an EVAL I have in the template (in between a [IFNOT...=] and [/IFNOT] logic tokens I might add) that does a calculation which includes a forward slash (the original error after all was "....Unexpected token "/"...."). Could this be the source of the problem ....?

[#EVAL VALUE="[Value1]/[Value2]"]

BTW I know for a fact that Value2 is NOT a zero or null value. Could this be the direction to drill into? Or does the error message indicate it is relating to a LOGIC token only?

One other point, this page works perfectly in most cases. It is only when certain parameter values are passed to it that it throws the above error.

Yeah, that eval looks like it might be the culprit. The error message is from Flee, which is the expression evaluator for the #EVAL tokens. There must be something it doesn't like with the / or arguments passed to it.

Richard, I've tracked it down. Indeed, the EVAL is the problem. A NULL value is being passed in some cases for the Value1. I know what to do fix it.