Cindy Brozyno | I'm one step closer. I ran SQL Profiler and did a trace of the service as I ran it. On the 7942 phones, it ran fine. On the 8941, I found the issue. I'm just not sure how to solve it. Below is the code that runs, then the SQL that goes through the trace. SERVICE PAGE CODE var input = Request.QueryString("input"); var input2 = input * 1; // I did this math to ensure that the data comes through as a number. The datatype of the field is numeric(15,0). sql=("SELECT * FROM dbo.vw_User_PinList WHERE PERSON_ID =("+input2+") "); TRACE RESULTS ON 8941 PHONE SELECT * FROM dbo.vw_User_PinList WHERE PERSON_ID =(Nan) select * from SELECT * FROM dbo.vw_User_PinList WHERE PERSON_ID =(Nan) (At this point, the user receives HTTP Connection failed, they try again, and this is what goes through: SELECT * FROM dbo.vw_User_PinList WHERE PERSON_ID =(73220) *********** I then changed the SQL query from requesting Input2 to input, leaving it as a string, to see what it was submitting. Here's what I found: TRACE RESULTS SELECT * FROM dbo.vw_User_PinList WHERE PERSON_ID =(%2073220) select * from SELECT * FROM dbo.vw_User_PinList WHERE PERSON_ID =(%2073220) User gets - http connection failed - tries again. SELECT * FROM dbo.vw_User_PinList WHERE PERSON_ID =(73220) So it looks like there is a Space coming through with the number, only on the 8941 phones. I'm going to try and add a "trim" statement to see if that works. Any other ideas out there? all help is much appreciated. Thank you. Cindy |
| Please sign in to flag this as inappropriate. |