[AccessD] Trap ODBC failures

William Hindman wdhindman at dejpolsystems.com
Wed Jun 17 07:30:03 CDT 2009


...I find that to be the rule rather than the exception these days
...trying to define the problem such that even jc can understand it does 
wonders for my understanding of it :-P

William

--------------------------------------------------
From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
Sent: Wednesday, June 17, 2009 3:45 AM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Trap ODBC failures

> It's amazing the number of times that sort of thing happens when you post 
> to this list.
>
> I was just composing a message to the list asking for help on a problem I 
> was having.
>
> Trying to write a nice clear explanation of the problem for the list made 
> me think a bit more
> about it and I realised that another approach would solve it.  It's doing 
> exaclty what I want
> now .
>
> Thanks for your help everyone :-)
>
> -- 
> Stuart
>
> On 16 Jun 2009 at 17:52, jwcolby wrote:
>
>> Never mind.  The form's error handler does this.  I was apparently 
>> testing the wrong form.
>>
>> Sorry for the ring.
>>
>> John W. Colby
>> www.ColbyConsulting.com
>>
>>
>> jwcolby wrote:
>> > How do you trap ODBC failures?  For example an index prevents a record 
>> > being added to a form, I get
>> > an ODBC error message (actually two) but it doesn't seem to be 
>> > occurring in code that I can break
>> > into and trap the error.
>> >
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 




More information about the AccessD mailing list