I've never seen this message before - you've got something strange happening there!  All I can suggest is that you remove transformations one at a time and keep trying ......

If you are writing the code as part of an ActiveX script, the & character is used to concatenate strings, not + (just to keep you on your toes)!

Suggest you modify your queries to remove any likelihood of ambiguity between column names.  Do this by prefixing the column name with the table name:

select tablename.columnname from tablename

If the table...

You can check this easily in EM.  Just open Security/Logins, right click the user of interest and select properties and you will see the default database.

You will not achieve this type of formatting with straightforward SQL statements - Ray M's solution, possibly with an additional ORDER BY clause so that you get everything in date...

update no

set status = 2

from n_order no join n_inv ni on no.id = ni.id

where (ni.tf is not null or exists (select bt.debtkey from banktable bt where bt.debtkey = ni.debtkey))

You haven't said what you want to update and what value, so I have left these for you to complete.

update no

set [field] = [whatever]

from n_order no join n_inv ni on...

Sure - right click on the Transform Data Task, select properties and then click on the Options tab.  You will see Max Error Count about halfway down the dialog box.

Don't be offended if this is blindingly obvious to you, but does the PHCR_Record table have an IDENTITY column defined?

Trial and error, walking around like a blind man in a dark room, is the way I did it.  Not recommended though

select item, max(StatusDate)

from table

Group By Item

These examples do not cope with > 2 transactions, which I believe (from the other thread which you posted) is the requirement?

This cannot be done in a single SQL statement.  If you definitely need it in this format, you'll need a chunk of code (examples of which appear elsewhere on this...

16 duplicates - on insert and on delete?

Is it a coincidence that you are inserting exactly 16 fields?  (I hope so!)

Have you got other triggers that may be causing some...

Are there always two transaction IDs for each StockID, or is the number variable (in which case, you want a variable number of columns)?