[AccessD] SQL - Copy * to another table

jwcolby jwcolby at colbyconsulting.com
Sat Feb 28 21:47:52 CST 2009


Thanks.

John W. Colby
www.ColbyConsulting.com


Bobby Heid wrote:
> John,
> 
> Look at these functions (SQL 2005+) and see if they would help:
> 	ERROR_NUMBER()
> 	ERROR_MESSAGE()
> 	ERROR_PROCEDURE()
> 	ERROR_LINE()
> 	ERROR_SEVERITY()
> 
> Bobby
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Saturday, February 28, 2009 8:51 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] SQL - Copy * to another table
> 
> I am using Try / Catch but my question is how people write the results to a
> log.  I would also want 
> to return the error string (not an integer error code) to my access
> application.  For that I will 
> have to dig in to the code I got from Charlotte.  IIRC she said that I have
> to send in a parameter 
> that is defined "output" or something like that.  I tried but never got it
> working.
> 
> My life is full of "gotta get the job out" and so I get enough to make it
> work and try to remember 
> to come back to it later.
> 
> 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.
>>



More information about the AccessD mailing list