You didn't take the clients business model into consideration;

the SBS solution is ideal for small businesses; minimal IT staff, and all that.

you should recommend that they get the SBS Premium...

learning how triggers work is absolutely valuable, so continue what you are doing.

you really need to grasp the use of the INSERTED and DELETED tables , and how you...

there's a quick fix for that, though; you can simply ALTER all your procedures. which will fix the sysdepends; if everything was rebuilt correctly, your dependencies are up to date.

note...

if you are using 3.5 Framework or above(or maybe...

Jason thanks for the salute...

i do something similar for comparing schemas and proc/view/function definitions, but i do it in an application, instead of as a procedure;

my logic: i want to compare functional definitions; i...

nope, EVERYTHING is logged, whether simple mode or FULL; it's just simple mode commits the changes right away and issues a check point.

you could consider having the procedure do it's...

a related post from long ago implies the bar code font had to be installed on the client?

that part i'm not sure, but Gianluca and i slapped together an example...

i wrapped it with a BEGIN / END to mark the limits of the trigger, and it seems to work fine.

based on something in my snippets, i added some extra...

the trigger, corrected for the syntax issue, seems to work fine for me; could it be you didn't reset the data back to teh original state when you were testing...

two tables, the INSERTED and DELETED tables are virtual tables that exist inside the trigger.

they are the data being inserted/updated/deleted into the table the trigger exists on...in your case,dbo.invoice.

they...

a WHERE statement is only valid with a SELECT,UPDATE or DELETE command.

you can insert with either values, or a select statement.

insert into tbTasks_New( AssignedToId)

values('Employee')

--OR

insert into tbTasks_New( AssignedToId)

SELECT

Employee

FROM YOURTABLE

where

Owner...

when you add a foreign key, all the pre-existing values are checked in the child table to make sure they exist/are valid in the referenced table.

if values exist that violate...

declare @val varbinary(max)

SELECT @val = HashBytes('MD5','123456')

print @val

--0xE10ADC3949BA59ABBE56E057F20F883E

SELECT

CASE

WHEN @val = HashBytes('MD5','123456')

THEN 'True'

ELSE 'FALSE'

END

simple syntax error.

queryout c\test.txt

i think that should be c:\test.txt; just missing the colon.