It is in parens, not brackets. Look...

Looks like you need to cast Timesheet.ProjectID as a VARCHAR(17) when comparing it to traf.WS_Job_Number.

Which may also require the COLLATE Latin1_General_CI_AS on traf.WS_Job_Number.

If you read the comment on that last WHERE clause, it can be dropped.

Nevermind, I figured it out. Missing a closing paren.

SELECT

timesheet.ProjectId as Job_ID_Timesheet,

timesheet.TaskCode as Cost_Code_Timesheet,

timesheet.Name as Cost_Code_Description_Timesheet,

...

Which one, my rewrite or your modifiy original code?

I think this is what will actually be required based on your original code.

SELECT

timesheet.ProjectId as Job_ID_Timesheet,

timesheet.TaskCode as Cost_Code_Timesheet,

...

Sorry, I may need to make a few more adjustments to your original code.

Here is your modified code.

SELECT

timesheet.ProjectID as Job_ID_Timesheet,

timesheet.TaskCode as Cost_Code_Timesheet,

timesheet.Name as Cost_Code_Description_Timesheet,

cast(null as varchar)...

If the data looks okay, we may need to add an ORDER BY clause to the code as well. I'm not sure how you'd want it sorted.

Just reads. I didn't see any UPDATE statement in your previous posts.

Okay, the following code parses and runs (with no result set generated, as I have no test data) in my sandbox database. You will need to make the appropriate...

Tried that on a table on my system here at home. You will need to go into the scripts and add the collation for the character fields as appropriate...

In the Object Explorer in SSMS, right click on the table and just follow the menu items until you script the table to the clip board. From there paste...

Your best bet is to contact Microsoft. My understanding of the license agreement is that you need to install all the components on the same server that you license...

Okay. Now all that makes sense. Thank you.