jwcolby
jwcolby at colbyconsulting.com
Sat Feb 28 07:19:19 CST 2009
I am kinda dense sometimes. Charlotte's code pops up an error message when something goes wrong. Duuhhhh. All I have to do is to return that to my calling code, log that to a table inside of Access - whatever. John W. Colby www.ColbyConsulting.com Bobby Heid wrote: > John, > > I'd look at @@ERROR and see what all information you can get from that. > There may be related items. I use SQL from .Net and just catch any > exceptions. > > Thanks, > Bobby > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Friday, February 27, 2009 7:57 PM > To: Access Developers discussion and problem solving > Subject: [AccessD] SQL - Copy * to another table > > Is there a way to get the SQL error statement back from a stored procedure > into Access? Or even > better is there a way to log the error statement inside of SQL Server? I > could read that table from > Access if I can log the errors. ATM I am just catching them in a catch > statement and PRINGing them > to a window in the query window. >