Cannot apply a function to the expressions

Query : Dim seqRcd = (From ajt In ContextFactory.Repo.abc Where ajt.id= 12489 AndAlso ajt.Seq = 1 Select ajt).FirstOrDefault()

Purpose: I have to check whether item with that id and seq exit or not. both id and seq are col names.

Tries I did:

1. using And rather than AndAlso 2. using Any() 3. Count()

Error : 2011-12-13 20:10:43,595 [44] ERROR user1- Cannot apply a function to the expressions (id= 12489 AND Seq = 1) and False at Mindscape.LightSpeed.Linq.Operators.BinaryFunctionOperatorBase.Apply(QueryExpression lhs, QueryExpression rhs, DataProvider provider) at Mindscape.LightSpeed.Linq.Sqo.CriteriaSqo.ExtractCriteria(IList1 rangeVariables, QuerySubexpressionCollection subexpressions, Expression expression) at Mindscape.LightSpeed.Linq.Sqo.CriteriaSqo.ExtractCriteria(IList1 rangeVariables, QuerySubexpressionCollection subexpressions, Expression expression) at Mindscape.LightSpeed.Linq.Sqo.CriteriaSqo.ExtractCriteria(IList1 rangeVariables, QuerySubexpressionCollection subexpressions, Expression expression) at Mindscape.LightSpeed.Linq.Sqo.Where.Evaluate(ExpressionVisitor visitor, MethodCallExpression expression) at Mindscape.LightSpeed.Linq.Plan.LinqQueryBuilder.VisitMethodCall(MethodCallExpression exp) at Mindscape.LightSpeed.Linq.Sqo.Select.Evaluate(ExpressionVisitor visitor, MethodCallExpression expression) at Mindscape.LightSpeed.Linq.Plan.LinqQueryBuilder.VisitMethodCall(MethodCallExpression exp) at Mindscape.LightSpeed.Linq.Sqo.First.Evaluate(ExpressionVisitor visitor, MethodCallExpression expression) at Mindscape.LightSpeed.Linq.Plan.LinqQueryBuilder.VisitMethodCall(MethodCallExpression exp) at Mindscape.LightSpeed.Linq.LinqQueryProvider.GetExecutionPlan(Expression expression) at Mindscape.LightSpeed.Linq.LinqQueryProvider.Execute(Expression expression) at Mindscape.LightSpeed.Linq.LinqQueryProvider.System.Linq.IQueryProvider.Execute[S](Expression expression) at System.Linq.Queryable.FirstOrDefault[TSource](IQueryable1 source)

We've been unable to reproduce this issue. It is possible that it relates to an already-fixed bug where Visual Basic was automatically inserting coalesce operations. Can you try to reproduce the problem with the current nightly build? If it still occurs, could you provide us with the definition of the entity which exhibits the problem (you can copy the class definition out of the generated code, we don't need to see the .lsmodel diagram itself)? Thanks!