Title: Message
(B
(B
(B Hi,
(B
(BYes, unfortunately
(BpgAdmin II does have trouble with DBCS and Unicode. Thankfully this is all
(Bresoved in pgAdmin III which handles different encodings with ease, as well as
(Blocalisation. Please feel free to try an alpha release from http://www.pgadmin.org/snapshots if
(Byou like.
(B
(BAnyway, to fix your
(Bcurrent problem, please delete the following registry key using regedit (don't
(Bforget to backup your system first in case something goes
(Bwrong):
(B
(BHKEY_CURRENT_USER\Software\pgAdmin II\Font
(B
(BpgAdmin should then
(Breturn to it's default settings.
(B
(BRegards,
(BDave.
(B
(B
(B
(B Hi!
(B
(B I've connected to Postgres 7.3 on Redhat 9 by pgAdmin
(B these days. Because pgAdmin and MS Excele can't see Chinese characters in the
(B same time, I changed the font setting in pgAdmin. Then I can't
(B loging anymore, but MS Excel work well still.
(B
(B I
(B tried to reinstall pgAdmin to get the default setting back but failed. For my
(B OS is XP traditional Chinese, the log listed below contants Chinese also. Mybe
(B the problem is due to double-bytes characters or unicode. After
(B all, please help me to get the default setting back and connect to
(B PostgreSQL again.
(B
(B Thanks!
(B 2003-06-20 09:21:36 -
(B ******************************************************************* 2003-06-20
(B 09:21:36 - Error(s) 2003-06-20 09:21:36 -
(B ******************************************************************* 2003-06-20
(B 09:21:36 - Error in pgAdmin II:frmConnect.cmdConnect_Click: -2147217842 -
(B $BVaCA`:n!#(B
(B
(B 2003-06-20 09:21:36 - Windows Version: Windows XP v5.1 build 2600 Service
(B Pack 1 2003-06-20 09:21:36 - pgSchema Version: 1.4.12 2003-06-20
(B 09:21:36 - MDAC Version: 2.7 2003-06-20 09:21:36 - cnPostgreSQL.State =
(B adStateClosed
(B Hammer
(B Lee
(B2003.0620
(B |
<<Glacier Bkgrd.jpg>>