DSXchange

So... you need to find the first occurrence of four numeric digits and then the single digit that follows immediately behind that after a 'dot'? Two separate fields or one? And is that always the case or if the four don't have a dot right there after them do you keep looking deeper in the string? Gi...

Exactly. Whatever it takes to make it work, fully automated, force that back on the source as a requirement once you figure it out. Been there, done that, got the t-shirt.

Only fall back to handling the quirks yourself if you absolutely have no other choice.

So... something like this?

Rather than wait for someone here, better to call support and ask them what is going on and have them explain to you how to accomplish your goal. That is precisely the kind of thing you / your company pay them for.

In other words, no.

You could always check with support, betting someone there has.

This issue looks familiar, perhaps this discussion might shed some light on the subject. Several people, myself included, have solved problems like this by using a symbolic link from where it is looking to where it actually lives.

:D

In other words... it's your choice.

Not supported here. However, are your attachments images, i.e. something you would be able to include 'inline' with your post? Regardless, you would need to host the files somewhere and there are many free sites to choose from. Then you could use the image or [img] tags to link in any images (gif/jp...

Time to involve support.

So... a hashed file lookup since there's no 'Lookup stage' in a Server job.

Didn't mean a Server job in this particular case but as mentioned earlier a Server Sequential File stage in a Server Shared Container in their otherwise Parallel job.

And I believe that a much simpler/elegant solution can be implemented using the Server version of the Sequential File stage. :wink: Suppress row truncation warnings. If the sequential file being read contains more columns that you have defined, you will normally receive warnings about overlong rows ...

SQL Server? Square brackets as shown in the first post. Perhaps this is something the connector should be able to handle, did you check with support? That warning doesn't come from ODBC but from the connector itself.