I am facing the problem of SSDBCombo (Which has multi column), While displaying properties of MS office 2016 word document into this control, It is showing Chinese and Japanese characters instead of MSWORD and MSWORD 2016, Data in combo box showing fine but selection of the data, it is showing juck characters. This is happening in Active-X(.dll) not in .exe.
It's only problem with MS Office 2016 Word(.doc and .docx not in .xls,.ppt),
Operating system : Windows 7,MS Office : Office 2016Visual Basic 6.0Data widgets 2.1 (SSDBCombo)
Could you please help us for fix this issue.
The SSDBCombo is pretty ancient, and it was retired long before Word 2016. It's not clear from your post exactly how you are reading the information from Word, or how you are populating the combo with that data.
My best wild guess is that Word is giving you Unicode or DBCS text and the SSDBCombo can't support displaying DBCS characters. There might be some way for you to change the encoding on the data, but I can't say for sure how you would do that - assuming that is indeed the problem.
Thanks for your clarification Mike,
We are reading the Word 2016 document properties by DSOFile.OleDocumentProperties, It is clearly reveals the ASCII characters like MS WORD 2016,Version 16.0,
We are able to printing that value into the Message Box without any junk characters. While assigning that value to SSDBCombo like
cboPaperFormat = .sPaperFormat
It is displaying junk characters(Chinese characters). It might the problem of MS Word 2016 integration with SSDBCombo.
Please provide solution on this.
Other than the ideas I mentioned above, I'm afraid I don't have anything else to offer you in terms of a solution. SSDBCombo was retired many years ago.
Clearly, if the control displays other text correctly and not the text from the Word document, there is something different about the text from the Word document. As I mentioned, it might be unicode or DBCS and you might have to convert it to something the SSDBCombo can handle. I suppose it's also possible that the text coming from the Word document it encoded somehow, but again, the solution to that problem would be to change (or remove) the encoding so that the SSDBCombo can display it.