Ok... Maybe I should have qualified my situation a bit better. I'm using an ODBC bridge software to connect to a Win2k/MsSQL 2k server. But DbMan (and the webserver) is running on a RedHat 8.0 box. I'm using Easysoft's ODBC - ODBC bridge software. Actually it works great!
I don't think that the problem lies within the connection but rather what DbMan is (or isn't) seeing back from the SQL server because the database entry works just fine when I take out the field trigger.
I have included the trigger that I am using below. Basically it just watches for whenever a new record is added. When it is, it fires off a stored procedure. Right now it does not return any value upon completion. Do you think DbMan SQL is looking for a return value? What is it looking for?
ON dbo.Claims
FOR INSERT
AS
BEGIN
DECLARE @RetVal int
DECLARE @_ClaimID int
SELECT @_ClaimID = ClaimID from inserted
IF UPDATE (ClaimID) EXEC AHSWeb.spClaimsRecordEval @_ClaimID, @RetVal OUTPUT
END
I don't think that the problem lies within the connection but rather what DbMan is (or isn't) seeing back from the SQL server because the database entry works just fine when I take out the field trigger.
I have included the trigger that I am using below. Basically it just watches for whenever a new record is added. When it is, it fires off a stored procedure. Right now it does not return any value upon completion. Do you think DbMan SQL is looking for a return value? What is it looking for?
Code:
ALTER TRIGGER dbo.Claims_Trigger1 ON dbo.Claims
FOR INSERT
AS
BEGIN
DECLARE @RetVal int
DECLARE @_ClaimID int
SELECT @_ClaimID = ClaimID from inserted
IF UPDATE (ClaimID) EXEC AHSWeb.spClaimsRecordEval @_ClaimID, @RetVal OUTPUT
END
