may not be the easiest way but you could drop the column, add it back in as 255 and then populate the data from col1 into the original with another...

use an alter table statement to add the 4 new fileds and then an update statement to set them as noted in the first post.

Are you inserting your one field into the clients 4 already existing fields or are you adding the fields to the clients table or are you adding the 4 new...

try this

select a.* from user_master a

join user_role_job b on a.user_id = b.user_id

join user_location c on b.user_id = c.user_id

join gen_location d on c.location_id = d.location_id

where b.job_id = '000000000102' and

d.location_id = '000009'...

WIthin DTS designer it is using the account that is logged into the workstation.

I've never run one through a proc but I would think that it is using the agent profile or the dts owner profile to to get the file.  You could...

well you know what they say about blind pigs and broken clocks

It would helpful if you posted what you already have done, the table structure, and an idea of the results you want back.  Are you looking for 2 seperate result...

You are right Noel, I had started down one path and didn't see the forest through the trees.

JB, I'm not sure if those are your actual field names but using...

We use ours to pick contest winners as you could probably tell from the code.

select v1.[name],v1.[year]+','+v2.[year],v1.number1+v2.number1,v1.number2+v2.number2

from

(select [name],[year],number1,number2 from t1) v1

join

(select [name],[year],number1,number2 from t1) v2

on v1.[name]=v2.[name] and convert(int,v1.year) = convert(int,v2.year)+1

so it is always  the first year joined with the year after. Are there gaps in the years and if so do they need to be accounted for so if...

How do you identify which rows you want to add together?  Is it always the next year? Are the years int or varchar?

We use domain accounts but the fact that several of you have access to the account for Remote Desktop is a bad idea.  How can you have an audit trail...

Might make a difference if you code has to be backward compatable with SQL Server 2000 B.C.