Scripted Import from tab file-Wrong Character Set

[alexliz]

I've just come across this bug, after many months of it working just fine. It's like this:

I scan my bank statements and import the line items in FMPA9 on MacOS 10.5.2. The text files from which I import are UTF-8 encoded, and it worked just fine. I had set up the params for the automated import using the 'Import Records' script step, and had specified from which .txt file, in what import order, and had also checked the 'Perform without dialog' checkbox. It was beautiful. I just made sure the right file was in place and clicked on my button.

Not so nice since yesterday, without having changed anything in my config. The 'Import Records' script step in my scripts reverts to 'Character Set: Macintosh' every time, even _after_ I've gone in the 'Specify import order' dialog and changed it to 'Unicode (UTF-8)' and then clicked on all the OKs I find on the way. Whenever I go back into my script to make sure everything is left setup like I want it, it's reverted back to 'Macintosh'. All other params (i.e. field import order, whether to 'Perform Auto-enter options while importing' etc.) are OK. It's just the Character Set that's consistently forgotten and reverts to the wrong value. Arrgghhh!

Any tips? Many thanks, people.

EDIT: I just opened up an old snapshot of my database, and it works fine. As a matter of fact, I went into the 'Specify import order' dialog of the Import Records script step and noticed that the 'Character Set:' drop down menu is all greyed out (but set at the right value, 'Unicode (UTF-8)', fortunately!).

Any ideas as to what exactly is going on?

Edited July 23, 2008 by Guest