Hi David - looks like you've cracked it.

I would suggest adding a WHERE clause too:

UPDATE    Subset

SET              Subset.Leadengineer = Contact2.ULEADENGIN

FROM         heat2.Subset Subset INNER JOIN

                      Goldmine.dbo.Contact2 Contact2 ON Contact2.Accountno = Subset.SupportInfo

WHERE Subset.Leadengineer <>...

Kenneth is correct about FLOATs.  But if EDEB is DECIMAL, the following WHERE clause should select only those with >2 d.p.'s.

where year(data)=2003 and round(edeb, 2) <> edeb

Why not just write a stored procedure and use that?  Usually no need to use DTS if all of your data is within SQL Server.

-- edit.  I misread your original...

If there is no DTSSource column to put your GV into, DTS does not know where to put it - which may be stating the bleedin' obvious.  That is why...

Jeff, I do not envy you that problem!

Does your solution have to remain entirely within SQL Server?  Might the client accept a DLL which you can call as an extended...

From the error message, this does not look like a problem with your GV.  You could check this by replacing the field4 line with

msgbox DTSGlobalVariables("g_RunNr").Value

and then run the step...

Actually, I should have left this thread well alone

But the original post contains two questions - that is how I came up with my...

Hi Mike

I think that your answer should start with 'No' rather than 'Yes'

--edit-- I think you were answering question 2 - I was...

Semi-automatically.  Select Tools/Options/Results and set 'Results to File' as the 'Default Results Target' and set the Results output format to CSV.

But you'll have to supply the filename and path.

If you...

Although the maximum column width in Excel is 255 characters, that is not the maximum length of data that can be stored in a column, which is 32,767 characters.

DTS will...

Can you post the script that generated the error?

This appears to be a reply to a non-existent message

So you are not seeing the tables in QA's Object Browser after creating them?  Have you tried refreshing the view?  Have you tried looking via Enterprise Manager?

Not sure about SQL7, but in SQL Server 2000, you could consider using

SET QUOTED_IDENTIFIER

to get round this.

This question is not detailed enough.

How did you create the tables - what tool did you use?  What tool are you using to view the tables?  Who were you logged...