Re: ADO exceptions

From: Fabio Dell'Aria (thesun_at_inwind.it)
Date: 05/11/04 

Date: 11 May 2004 01:22:43 -0700

Brian Bushay TeamB <BBushay@Nmpls.com> wrote in message news:<m8sl90la8crces5bhjdl8ak7963uckvbvu@4ax.com>...
> >I'm using a MS SQL Server 2000 with ADO components as front-end.
> >When the server send an error, only a generic message error 'OLE error 80040e2f' I obtain.
> >Items in adoconnection.errors[] are empty.
> >
> >However it works fine in other machine.
> >How can I to secure a uniform behavior?
>
> I believe there was a problem with ADO 2.6 behaving like this when the local
> identifier in SQL was different from what was set in Windows. This was fixed in
> a subsequent update to ADO. If you are using ADO 2.6 I suggest you get the most
> recent update.

You can try EurekaLog (www.eurekalog.com).

EurekaLog is an add-in tool that gives to your application (GUI,
Console, Web, etc.) the ability to catch every exception (even those
raised by memory leaks) and every infinite-loops/deadlock bugs,
generating a detailed log of call stack (with unit, class, method and
line #), showing and sending it back to you via email. 

--
Best regards...
Fabio Dell'Aria.