January 9, 2008 at 9:37 am
Hi,
I am having some trouble using ASCII encoded text files as flat file sources. If I receive Unicode encoded files, everything works fine and dandy. But all trouble starts when I try to process an ASCII file.
I have tried changing the Code page property in Flat File Connection Manager Editor to ANSI Latin by unchecking the Unicode checkbox, and it hasnt worked.
Is there a way to modify a file's encoding in SSIS?
January 9, 2008 at 10:10 am
I don't know how well this will work via copying this to the forum, but I put the following (we call it the BOMB) into my TXT or SQL files where I want to have UNICODE strings that handle localized data. If copying the 4 characters and a carriage return line feed into your file does not work, I may be able to save a file and email it to you. Send me a note if you need that. For automating this, you could put this string into a file of its own and then copy this with the files you need to process to create a unicode version of your file. I know coping files with this bomb and files without it works fine because that is how my DB build process works, but the final file will only be UNICODE if the BOMB is the first line.

Hope this helps or I hope someone else has a better way.
Disclaimer... I have no idea how this works, I just use it. When I do a google search for UNICODE and BOMB I do get a bunch of hits, but I did not find any details when I was quickly looking around. Sorry.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply