> From: Doug Chamberlin
> At 12/3/2000 09:36 AM (Sunday), Syarzhuk Kazachenka wrote:
> >IIRC, in version 5, contrary to what documentation said, giving execute
> >rigghts to just the parent stored procedure didn't work. I have no idea if
> >that was fixed in 6.
>
> This is wrong info. The bug is fixed in 5.6 version, so I assume it is also
> fixed in 6. I'm not sure exactly which version the fix first appeared in.

Here is explanation from David Schnepper.

Ivan
prenosil@...


Date: Wed, 23 Jun 1999 14:45:19 -0400
From: David Brookstone Schnepper
Subject: Re: Volatile GRANTs

There were bugs in this area that I fixed right about the time 5.5 was
finalized.
I don't think they were included in 5.5 - but are in 6.0.
The bugs dealt with
User X has execute on Proc A
Proc A has execute on Proc B
There were some instances where user X would also need execute on Proc B
for successful execution. A simple bug in how the transitory permissions
were calculated.
I think (from memory) the same bug would apply in your case
(Table B instead of Proc B).
It's also consistent with your "works initially, then stops working".
It had something to do with the order of calculating permissions.

There was no workaround, other than what you already discovered of
granting rights to public.

Dave