OK, I got the UPDATE problem figured out as well.

It seems it is not possible to use a CASE statement where you use multiple paranmeter references. It will just increment...

Right...

The INSERT works in another package. I was disgusted with the problem package and started to work on something else. And here it works, don't know why. I'll have a...

Alas Nite_eagle, your solution does not work, I receive a syntax-error.

I really don't get it and could use an example of how to use parameters in an OLE DB Command....

This is horrible, never thought of that... I begin to doubt myseklf:w00t:

So how would I go about using parameters in an update? I would think something like:

UPDATE TABLE

SET Field1 =...

I see what you mean. I'll give that a try.

Tnx,

Tnx for answering, Pow, but I'm not sure what you mean. I don't think there is a variable which can be attached to a part of an SQL statement.

1 way...

Tnx for answering all.

OK, got it, tnx for explaining... but I don't get it. As far as I can tell nowhere is there an EXPLICIT comparison between the Integer(either @Ind or @PersoonID) and...

COPPersoonID is INTEGER, it's the key of that specific table. CRMID is the unique-identifier datatype, just an attribute in that table.

I get this strange message when using the CASE construction as given by Ahmed. 1 of the possible fields to select is datatype UniqueIdentifier. When I run this statement:

DECLARE ...

Tnx for the help, all. I'll have to look into this tomorrow, it is still not clear to me, but I'll get to it.

Tnx again,

Found a solution on this site. Register a few dll's eem to do the trick.

Don't ask why...:hehe:

Tnx for answering. I suspected as much. Makes me wonder in this case why I need to use a Conditional Split to seperate the records. I could direct them into...

Right....

There is indeed a different collation on some columns. I'll have to delve into that.

Tnx.

Tnx guys,

I tried IS NULL but I guess I did something wrong there. This works & helps. Tnx again.