That makes sense. If that part of the Procedure is never executed you will never get the error!!

Cheers

PK this kind of problem is typical  at run time only when alias are not used (which is not your case)

About the error at compile time is not going...

This error is ussually caused due to a MASSIVE number or records returned to the Client side. Please either Limit the number of records returned or increase the RAM of...

Can you post the Offending code

Yes that was my sussestion but wasn't expecting high frequency Officially you can't run a job  in intervals of less than a minute. There...

the problem with creating jobs on the fly is that you are assuming alot!

1. The Account that created the job needs access to msdb (something I don't like particulary from...

NICE Job Rudy! I knew I had seen that before

Farrell,

Besides What Ray Already mentioned about the wrapping Transacrtions command being unnecessary your search filter must be:

WHERE Old.Dollars <> New.Dollars 

      OR( Old.TextValue IS NULL AND New.TextValue IS NOT NULL) ...

the IF UPDATE() will speed up things in case where no action is needed

Yep Got Hit by timeouts more than once today too

Farrell,

You are better off separating this into two triggers one for insert and one for update. IF UPDATE() is meant for UPDATE Triggers. The trigger should ALWAYS be coded to...

to start a job from a Trigger is bad. Jobs are NOT re-entrant, can you imagine what would happen if you try to start a job that hasn't finished yet?

I...

Ah FoxPro... I have some fun memories and some not so fun from Developers that I used to work with. mind you FoxPro SQL SUCKS!!!!!!!!!

It has been a while since I have been in charge of Full Model implemetation  but DBArtisan of Embarcadero, ERWin of Computer Associates and Sybase Power Designer are the most...

Igor {} can be used also to call ODBC scalar functions and the {} are there for backward compatibility and yes, they WORK!

an example of such functions is:

select {fn ucase(...