active lock?

[tsp1lrk]

Hello,

I'm just updating my cold fusion forms to use a SQL dsn rather than an Access one. I noticed that as soon as I change it, upon my login page I now get this error when someone trys to login:

Error Diagnostic Information

An error occurred while evaluating the expression:


Session.LoggedIn = FALSE



Error near line 1, column 7.
--------------------------------------------------------------------------------

Symbol Session.LoggedIn is in a scope that contains data shared across threads and cannot be accessed without an active lock



The error occurred while processing an element with a general identifier of (CFSET), occupying document position (1:1) to (1:32).

What does this mean??? In Access, never experienced this error, only since I'm now connecting to a SQL 7.0 server.

Thanks,
Lisa
UPS

 

[CFDude]

It really doesn't sound like a db issue -- the error indicates it is in a cfset -- it sounds like you have full checking turned on for your session variables. This is in the Locking section of CF Admin.

Which leads to the next question -- are you not using CFLock around your session variables? You should be doing this -- try:

<cflock scope=&quot;SESSION&quot; type=&quot;EXCLUSIVE&quot; throwontimeout=&quot;Yes&quot; timeout=&quot;5&quot;>
<cfset session.loggedin = FALSE>
</cflock>

 

[tsp1lrk]

Thanks so much! I had just read another post by someone with the same problem,I don't know how I missed it, Yep, I added those tags in there and it worked. I have another problem, with SQL/CF. I'm searching on names and I came up with the error:

ODBC Error Code = 37000 (Syntax error or access violation)


[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid operator for data type. Operator equals boolean AND, type equals nvarchar.


SQL = &quot;SELECT * FROM tblEmp, tblDpt WHERE strDptIDFK = strDptID AND (strFName LIKE '%Lisa%' OR strLName LIKE '%Lisa%' OR strFName & ' ' & strLName LIKE '%Lisa%') ORDER BY strDptName, strDptIDFK, strLName, strFName&quot;

This worked no problem before with Access, is this a SQL problem?

Thanks so much,
Lisa