Ok the problem I have now is that I have the date I want as my global variable, but the query that imports from access at some point sees it...

Yes both dateclocking fields are datetimes.

Forgot to mention that I am moving the data from a table in an access 97 database called clockings which gets updated. The new...

Excellent thank you, all sorted now. Knew I needed to use a global variable but wasnt quite sure how, cheers

I have solved the problem now, it was my access referneces one was missed so I cleared its box and it all worked fine.

Thanks Noel worked fine. Although I only read it after I had written out code for computed columns which was getting on for 1000 lines lol. ONe last problem though...

I feared that was the case when i first started writing the query hence tried to use a trigger instead. I have 12 calculations derived one after the other so...

Can't use computed columns as you can compute one column but then you can't derive another computed column from another computed column.

Wrote a trigger which if it worked would be...

Can't use computed columns as you can compute one column but then you can't derive another computed column from another computed column.

Wrote a trigger which if it worked would be...

why would the insert run for each row updated but the calculations not?

CREATE TRIGGER trigOrderDetail ON [dbo].[Order Detail]

instead of insert,update

AS

declare @ProdWeekend datetime,

@Day varchar(20),

@ProdWeek datetime,

@ProdDay varchar(20),

@prog datetime,

@ProgDay varchar(20),

@CalWeekend datetime,

@CalDay varchar(20),

@Cal datetime,

@PresAssemWeekend datetime,

@AssemDay varchar(20),

@PresAssem datetime,

@StockWeekend datetime,

@StockDay varchar(20),

@Stock datetime

declare @OrderID...

I have a string of 12 columns, each derived using the expression calculated in the last. Decided a trigger on insert will be the best way forward????