Changes to stored procs don't affect passthrough query

C

Carol Grismore

When I make a change to a stored procedure, it looks to me like the Access
passthrough query doesn't update, but keeps running the old stored proc
somehow. Am I seeing things? Is there a way to let the Access query know
that there's been a change to the stored proc? TIA, all.
 
L

Lynn Trapp

C

Carol Grismore

Actually, we have Sybase, which is a lot like SQL Server. I believe you when
you tell me that this shouldn't be happening.

What led me to the conclusion that this was happening was a simple procedure
I wrote to show me all the users in our database who had no role (find all
users with a blank field in a table). The Access passthrough query for this
procedure displayed valid information.

Later, when I amended the procedure to include people with no email address
as well, the Access passthrough query continued to show people with no role,
but failed to show people with no email address.

I created a new query, pointing to the same stored procedure, and the new
one does show people with no email address, in addition to those with no
role, yet the old query, pointing to the same procedure, still shows only
people with no role. Clearly, there's something I don't know about going on
here.

Any thoughts?
 
C

Carol Grismore

Yes, I sure have, and lots of permission things on the Sybase side and in
Access, and other really random things. I've never run into anything like
this before, and I'm quite sure it's really happening. At this point I don't
know what to do next; maybe I'll just start drinking or something...

Actually I think I'm going to try to go around the problem by having the
procedure run from Access but create a table on the Sybase side that I link
to the Access database. Just so we get back on track, you understand, not
that I'm giving up!

:eek:( Yeah, I'm giving up; I don't have time to do anything else right now.

If I ever solve this one, I'll let you know.
 
L

Lynn Trapp

Top