Using the SQLOLEDB driver instead of the MSDASQL ODBC driver did the trick. Once more the world is spinning on its proper axis. Thanks very much.

The connection string is passed in as a string value aCnString in the following code:

' Get Connection Ready

Set cn = Server.CreateObject("ADODB.Connection")

Set rs = Server.CreateObject("ADODB.Recordset")

cn.ConnectionString = aCnString

Response.Write "ConnectionString 1: "...

Ok, this jives with the little research I have done. Some other databases allow you to define custom error messages with each foreign key constraint but this doesn't appear...

Thanks for the detailed reply. A further question: Suppose I have a delete that can violate several foreign key constraints in different child tables, can I easily determine...