We'll see what he has to say... maybe even he doesn't really know what he needs at the moment.

I think you'll have to track those changes in the sp before firing the main update statement. I don't see any other way of doing that.

Can you open the profiler, try to access the problem tables and paste the queries sent by access 2k3 on the server?

You never actually use this :

Select @UniqueId=Scope_Identity(), @Err = @@ERROR

you must select the err code after EACH INSERT

also is the first insert's id an identity column??

Not really... what do you need to do exactly?

Insert into table (name) values (women''s group) will work. But you are better off using stored procs to do this work.

Check out the sql injection section of this article...

Well that's just it, those type of columns are not included in the inserted and deleted tables because they can be way too big.

Select case when datepart(dw, GetDate()) < 6 then A.WKDAY else B.WKEND end as WEWD from ...

Yup : application's job. String manipulation is much easier on vb 6 and .net than sql server. And it is not the job of the server to do...

Still the job of the application to transform the data for presentation... the db should only store and ship the data, nothing more.

Application's job to do that.

Assuming it comes in only one table...

Select DATEPART(hh, CrDate) as Hour, count(*) as Total from dbo.SysObjects where XType = 'IF' GROUP BY DATEPART(hh, CrDate)

there's a script to generate the insert statements :

Help us help you

Can't convert it without sample data and expected results to make sure we're ok.