Do you remember which proc failed??

This could be a very simple fix but I just didn't think about it :

try adding another return somewhere in the proc.

(Long story short,...

I don't think they would compile if the table name is correct. But I can't test from here, maybe tomorrow.

I'm still a first year programmer... I'm just real good in tsql, I'm not a god. yet .

Search on these boards..

sp4 awe bug should give you something like this :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=182669

What happened when you didn't reboot?

Find a problem a few months later when you have to reboot?

Care to elaborate on this?

As I said, this MIGHT be it, but I would expect to have this problem reoccuring once in a while, not just at the first execute after the proc is...

So I'm still a show off??

hmm.. I don't see any reference to the deleted table in here :

UPDATE LogOn

SET LogoffDate = GETDATE()

Where

logon.scrnnbr = deleted.scrnnbr...

Just a thaught, I've learned that temp tables can cause locks in tempdb when the procs are run... Maybe that would be something else to check but I doubt that...

Here's an exemple of the join you need to write... Msg back if you need some help.

CREATE TRIGGER LogOn_Delete

on ACCESS

For

DELETE

as

SET NOCOUNT ON

UPDATE L

SET LogoffDate = GETDATE()

FROM LogOn L inner join...

Well I'm out of ideas... maybe somebody else will figure it out.

Maybe just for luck, can you post the code of the stored procs?

I'm trying to stop... but I like the users to have the right answer.. sorry about that .

What happens if you backup the log every 10 minutes?? maybe the spikes will be much shorter and it would cause any problems...

Should this update have a join to relate the 2 tables??

Also I would make sur that this is not causing you the error

: EXEC master.dbo.xp_cmdshell 'copy "C:\Documents and Settings\Administrator\My Documents\Commander\AutoPrintPackingLabel.txt"...