**

I got my DBA involved and we ran a trace. It turns out that it was my "on modify" filter that was causing the problem. The filter action was to run a select statement against the database and one of the fields it read was status. I used the text value of "closed" instead of the integer value of "closed". Once I changed my SQL statement I was able to manually save the request with no issues.

-Rick

-----Original Message-----
From: Rick Westbrock
Sent: Tuesday, December 30, 2003 2:56 PM
To: 'arslist@arslist.org'
Subject: SQL error on modify

I recently created a regular form (EscalationTriggers) so that I could use an escalation to fire off "on modify" filters to count requests on another form (see the previous " Building an escalation qualification based on table contents" thread that I began.)

I have run into a bizarre problem that I've never seen before. My escalation was not modifying the request in EscalationTriggers like it should have so I decided to manually modify the request. I was able to modify it once but when I went back to modify it a second time I got this error message:

ARERR [552] Failure during SQL operation to the database: The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. (SQL Server 3903)

The good news is that I appear to have found the cause of the escalation action (modify) failing. The bad news is I can't figure out how to get around this problem. None of my other forms are acting up like this and the only fields that I added to the default ones are one each of date/time, character and integer.

I am running ARS 5.1.2 on Win2K and SQL Server 2000 on Win2K. Has anyone else run into this issue or know how to solve it?


Rick Westbrock
Store Systems WAN Administrator
Petco Animal Supplies (IS/Store Systems)
rickw@petco.com
v: 858-453-7845 x3552 f: 858-909-2789

This posting was submitted via the Web interface