DSXchange

kaps wrote:In Parallel it shows like 002250{ whereas in server it shows correctly like +00225.00

Those are two different flavors of the same correct.

To me, there's a lot of "depends" in your answer. What happens next with them?

Oracle uses a double-quote as shown, guessing it confused the bind variable mechanism in the connector.

Some questions, mostly out of curiosity, since this seems like a somewhat odd request to me. What aspect of the users are you attempting to maintain, strictly their security roles? What is this 'external system'? What registry are you currently using - the internal one, LDAP, local O/S?

Post the entire, unedited error message please.

Yah, or that. At least then you'd have more information to give to support.

You mean SIGINT and I would involve support for something like that.

It's BASIC code so anywhere that can be used... routines, job control, etc.

Let me chime in with, even if you can work around it, having a table with a column name that is a reserved word falls firmly in the Not A Good Idea camp. IMHO. Have you verified that is indeed the problem? If the column is nullable, don't include it in the DML and then see if it works... as a test.

Do you understand how that 'did it'?

Use the Convert() function to strip them from the field by replacing them with '' - an empty string.

We know what you need. What is your target data type? It needs to be a string and I suspect you are putting it into a number which strips the 'not significant' leading zero. If you are using a string then post the actual code you are using, copy/paste from the transformer (don't hand type it).

Not sure what this conversation has to do with SQL Server.

So what happens if you use the code I posted, what is the resulting string?

Cats?

Why not just do it all at once?
Now, that's off the top of my dusty head but should get you pretty close. That may leave a space between the two but you can use Convert to remove it.

Time to involve support, if you haven't done so already.