🚀 go-pugleaf

You could work backwards from the error message if every constraint message
was unique.

Constraint messages can be obtained via the TAdoConnection.OpenSchema call
to siCheckConstraints.

If your update was to a TAdoDataset rather than through an UPDATE SQL query,
you could look at the Error parameter of the RecordChangeComplete Event but
there is no Delphi help on that. On my system it is a pointer. Refer to MS
SDK.

If you would like to know more about the information that can be extracted
from your database, the tool below allows OpenSchema calls to be made in a
GUI. As you will notice if you use it, Check Constraints have no criteria
for table and fields. But it is possible to establish the table and field
from the constraint name (in Access at least)...as it includes the table and
field name within it e.g. CONSTRAINT_NAME= [country].[capital].validation
CHECK_CLAUSE= "<d"

--
Michael Collier Bsc (Hons) Comp Sci
ADO Support Tools.
Download Free Fully Working 30-Day Trial in 7 Minutes From...
http://www.adoanywhere.com/download/aaBrowse2_6.zip

All information in this message is provided 'As is' and without warranty of
any kind. http://www.adoanywhere.com