Questwizard
Newbie
Posts: 4
Registered: 11-06 |
The only thing I can come up with is that its some sort of character set problem related to Visual Basic (It's practically famous for having VERY bad internationalization support). You've got the EXACT same errors and stuff that I have with it. Check and see what language you have set for non-Unicode programs in the Control Panel.
To do that:
Head on over to the Regional and Language Options in the Control Panel, and click on the Advanced tab. Your selected language will be under the Dropdown for the Language for non-Unicode Programs.
If its set to English, it's probably not an encoding issue, but if it isn't, you might need to set it to English (United States) and reboot. Then see if that fixes it. (Be warned your text in some older programs (and some newer ones) might mess up and display as garbage, but at least DB should work properly. You can always switch it back when you're not using DB anyway. Yes, there is AppLocale that can supposedly switch it temporarily, but it does NOT work at all, because it isn't DB you need to run in English settings, its the VB runtime DLL's, which is something AppLocale can't do.
NOTES:
(I've figured out through some trial and error before that DB hates most non-English locale settings (thank Visual Basic's habit of converting everything to ANSI for all the overflow errors), and will do nothing but crash like that if you try to do anything. It does the same thing for me with the locale set to Japanese. If I turn it back to English, I never have a problem other than my keyboard layout going weird because I use a Japanese keyboard.)
Last edited by Questwizard on 11-11-07 at 16:37
|