Hello all --
Here's a bit of code that was working up until today:
Response.Write("<table>"
for i = 1 to numberOfSVPsToDo
Response.Write("<tr><td>"
myFilterString = "svpNum=" & cint(svpsToDoArray(i-1))
rs.Filter = myFilterString
..............
and so on...
Now rs.filter = myFilterString is causing the subroutine where it's located to simply stop executing, and jump out of the sub... picking up execution right after where it's called. It's working perfectly on my development server... it WAS working perfectly on my production server up until this morning when the problem was reported.
I simply can't figure out what to do to get this thing running again. There are no errors or anything -- just an incomplete execution of the subroutine followed by the rest of the page's output.
I'm at a real loss here, and my client is waiting, so if anyone out there has experienced this type of wierdness in the past and could shed any light on the situation, I would appreciate it.
Thanks -
Paul Prewett
Here's a bit of code that was working up until today:
Response.Write("<table>"
for i = 1 to numberOfSVPsToDo
Response.Write("<tr><td>"
myFilterString = "svpNum=" & cint(svpsToDoArray(i-1))
rs.Filter = myFilterString
..............
and so on...
Now rs.filter = myFilterString is causing the subroutine where it's located to simply stop executing, and jump out of the sub... picking up execution right after where it's called. It's working perfectly on my development server... it WAS working perfectly on my production server up until this morning when the problem was reported.
I simply can't figure out what to do to get this thing running again. There are no errors or anything -- just an incomplete execution of the subroutine followed by the rest of the page's output.
I'm at a real loss here, and my client is waiting, so if anyone out there has experienced this type of wierdness in the past and could shed any light on the situation, I would appreciate it.
Thanks -
Paul Prewett