FiveTech Software tech support forums

... of xbrowse, that format has problems ( using the DEFINE and then ADD COLUMN ). I had used that hundreds of times in my application and all were broken. I had to recode every one of them to the newer, not yet documented, format. Here is a sample of the newer format I was told to use. I am using ...

... problems still active with xBrowse: 1) Positioning with ADS to bring focus to a specific row is failing to work correctly. 2) Set Checkmark is broken in 16.01 but worked in 15.12. 3) Column spacing using the old format of ADD column TO a browse does not format the columns correctly. This may ...

... I'm doing here is substituting code that is actually more compact for longer lines of code. I do each one individually, and thus nothing is "broken" So here is another section of code that we have to add to all browses. Are any of these covered in the COMMAND structure you are using: ...

Kim,

It seems as a Harbour problem (not related to FWH) that should be reported in the Harbour users group:

https://groups.google.com/forum/#!forum/harbour-users

I am sorry I can't be of more help on this

Mr.Antonio,

Yes...
It works, and show Correct results(Korean alphabet) when compiled with xHarbour.

But, when compiled with Harbour, Korean Alphabet was broken..., like... "??????"

Thanks.

Kim,

Do you mean that this code is properly working with xHarbour and fails with Harbour ?

Code: Select all  Expand view

cSQL := "SELECT code, iscode,num, name FROM CD_PERSON where name='홍길동' "
oRs:Open( cSQL, oCn )
 

Mr.Antonio Linares, Thanks for your comments.. :lol: What I hope to solve is MSSQL matter... I mention that , with same codes , there was no Korean Alphabet problem when compiled with xHarbour.. Through comment of "No problem with xHarbour", I expected some experts may think about problem....

Kim,

You were talking about SQL and then you start talking about hbzip

How are they related ?

You don't need to pay for tech support as these forums are free for FWH users

Dear Hua, Thanks so much for your comment... And, I have visited the page according to your advice... Even in my point of view, It was the information related to my problem... But, I am only beginner.., it was difficult for me to use ... Mr.Antonio, Is there service to linking certain needs with per...

Kim, I'm just guessing here but you might want to have a look at codepage - http://harbourlanguage.blogspot.my/2010 ... epage.html

HTH

Dear Sirs,

As mentioned abode, in Harbour, Korean Alphabet was broken in MSSQL (or "ADODB.Connection"),?,
but, in xHarbour, it was possible to use Korean Alphabet in MSSQL (or "ADODB.Connection")..

Where is the difference ?

Thanks...

Mr.Antonio, I've just compiled my source file with xHarbour... And... I found that there is no "???????"...with Korean alphabet... The only thing I've done was "replacement "HBZIP.LIB" with old version of HBZIP.lib" since there was following error with recent HBZIP.LIB....

Thanks.. Mr.Antonio Linares...

I've tried "N" prefix already...
But, there was no change...

it there other option?

Kim, You should use the N' prefix to indicate that you're searching for a Unicode string: SELECT * FROM dbo.tblArticle WHERE name LIKE N'%......%' Otherwise, you're converting your search string back to non-Unicode and then searching.... http://stackoverflow.com/questions/11258129/sql-server...

Dear Sirs, I think there might be Character-set problem.. So, I inserted following sentence to see structure , characterset.. cSQL:="SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA='dbo' AND TABLE_NAME='PERSON'" And, get following structure.. Please see CHARACTER_SET_NAME,COLLA...