Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

.filter causing subroutine to bomb out

Status
Not open for further replies.

link9

Programmer
Nov 28, 2000
3,387
US
Hello all --

Here's a bit of code that was working up until today:

Response.Write(&quot;<table>&quot;)
for i = 1 to numberOfSVPsToDo
Response.Write(&quot;<tr><td>&quot;)
myFilterString = &quot;svpNum=&quot; & 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
penny.gif
penny.gif
 
For anyone that's interested, here was what was causing it:

This morning (before my second cup of coffee), I imported a table to the production database, replacing one that was there that had old data in it.

The table that was imported had an owner other than dbo -- and so the view that was being opened to display the data was referencing this table with no owner prefix (i.e. dbo.tableName)

Now, you would **think** that this coulda, shoulda, woulda thrown an error, but it didn't -- it just sat there like a lame duck and did nothing.

At any rate, once I put the owner prefix on the table name in the view, everything is now working perfectly, and here's the moral of the story:

If something suddenly doesn't work, SOMETHING changed. It might not look like it, it might not smell like it, and you might swear on your mother that nothing did, but SOMETHING changed. Trace your steps, and find it, because that's where your problem is.

I'm going to go have a heart attack now.

%-(
paul
penny.gif
penny.gif
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top