Classic ASP, SQL Server, Windows Azure, Radio Button UPDATE SET Command - Unexpected Behavior

I inherited the classic ASP application and switched to Windows Azure, SQL, and everything works fine. Also, one weird issue you might know about?

Scenario

The choice of data order lines by matching a unique identifier is present in the user interface. Two lines per set. One is already marked in the "MasterSelect" field with "Y". The ASP code invoked using the OnClick radio button clears (or should) both fields in both records, and then sets the new record field to "Y", whether it is the top or bottom selection. Switch if you want.

Works like a charm (local) and halfway running on Azure.

**(local)** ('x' = choose radio button)

x #1 -->  'Y'
  #2 -->  ' '

  #1 -->  ' '
x #2 -->  'Y'

x #1 -->  'Y'
  #2 -->  ' '

**(Azure)**

x #1 -->  'Y'
  #2 -->  ' '

  #1 -->  'Y'  <--- (Should be blank)
x #2 -->  'Y'

x #1 -->  'Y'
  #2 -->  ' '

Here is the code:

' If updating the master select field then need to clear all previous selects for that dupid
if updfield="masterselect" then
    strSQL = "select FileName,DupeID from OnLineContactsM where OnLineRecID=" & keyvalue
    cn.execute("exec insertactivity '','','ajaxUpdate.asp','" & strSQL & "'")
    set rs=cn.execute(strSQL)

    if not rs.eof then
        fn = rs("FileName")
        DID = rs("DupeID")
        strSQL = "update OnLineContactsM set MasterSelect='' where FileName like'" & fn & "' and DupeID='" & DID & "'"
        cn.execute(strSQL)
        'cn.execute("exec insertactivity '','','ajaxUpdate.asp','" & DID & "'")
    end if
end if 

, , , . , , () (), - ?!?!?

, , - , , , reset , , () . , , , , Azure , .

, , , - , , , , , -, .

(, , ..), , , . - .

- - , ?

!!!