>Okay...just tried that...no difference. Not sure if there are any registry settings I should be searching for.

Seems to be it's trying to position the cursor at the end of trimmed string - i.e. if you click beyond the last non-space character, it moves the caret in front of the first character. If you have some text in the field, you can click anywhere inside the field and it will stay there; try to click beyond the last character and you're zapped to right behind that last character.

Seems like the necessary behavior for Varchar fields - the bug being that it extends to character fields. But I could bet I had this on a really long character field where it kept going home no matter how much text was in there.

As to the resource file issue, the behavior is the same here (with my age old foxuser) and on the other machine (where foxuser was zapped this Tuesday).