FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

I checked in a fix yesterday to handle INT_CONTINUE correctly when MSDBLIB
is defined and an error other that SYBETIME is being handled.  I think this
issue can be considered closed for now.

On a different but related topic, I think we also need to handle INT_EXIT
differently when MSDBLIB is defined.  As Jim pointed out, Microsoft says
that when this code is returned from an error handler "with the Microsoft
Windows operating system", it is treated as INT_CANCEL.  My opinion is that
since "MSDBLIB" is used for API-compatibility with Microsoft's DB-Library,
we should behave the same way even though we probably aren't running "with
the Microsoft Windows operating system".

Any objections?

Cheers,
--nick


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.