Debugging Stored Procs

External Since: Jun 17, 2008 Posts: 20

Hi Guys,

Just a quick question on the availability of debugging stored procs.
At the moment, if I have an issue, what I do is firstly work out what
the SP is doing. Then I look over it, looking for an abvious error
(We're assuming wrong data is being returned). If I can't spy the
issue, I then create PRINT statements in the SP and run it, checking
values as it goes through - and after a lot of crying, head banging
and writing on these helpful groups - the issue gets spotted and
resolved.

I'd like to know if there is a better way to debug SPs. I assume there
is no way to 'step through' the code. I'm not sure why that's not
possible. It would indeed be pretty funky to 'F9' your way through the
SP, and hoving over variables to check their values.

I'd like to know what your ways of debugging are, and if mine is the
most efficient use of time.

Thanks guys,
Craig

External Since: Sep 29, 2008 Posts: 54

On Sun, 23 Nov 2008 15:22:24 -0800 (PST), Cralis <info.RemoveThis@listerhome.com>
wrote:

Actually there *is* as way to step through a sproc's code. If you have
Visual Studio. Not sure if the free Visual Studio Express Edition
offers the same benefits.

-Tom.
Microsoft Access MVP

>Hi Guys,
>
>Just a quick question on the availability of debugging stored procs.
>At the moment, if I have an issue, what I do is firstly work out what
>the SP is doing. Then I look over it, looking for an abvious error
>(We're assuming wrong data is being returned). If I can't spy the
>issue, I then create PRINT statements in the SP and run it, checking
>values as it goes through - and after a lot of crying, head banging
>and writing on these helpful groups - the issue gets spotted and
>resolved.
>
>I'd like to know if there is a better way to debug SPs. I assume there
>is no way to 'step through' the code. I'm not sure why that's not
>possible. It would indeed be pretty funky to 'F9' your way through the
>SP, and hoving over variables to check their values.
>
>I'd like to know what your ways of debugging are, and if mine is the
>most efficient use of time.
>
>Thanks guys,
>Craig