Results 1 to 10 of 10
  1. #1
    2 Star Lounger
    Join Date
    Feb 2002
    Posts
    155
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Using Word 9.0 object library (A2K)

    Access 2K isn't IME(Input Method Editor)-aware, but Word 2K is. In fact, IMEmode property and function as well as IMEStatus function are available in Word if one were to search for them in the VBE's help in Word. I need IME function in Access. Can I reference Microsoft Word 9.0 Object Library in Access and subsequently use the IME functions available in Word? Excuse my naivete but I think it is possible on paper.

    PS: I am feeling a little guilty on this day (11/Sept) that my mind is focussed on Access instead of thinking of those sad people who lost heir loved ones exactly a year ago.

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Using Word 9.0 object library (A2K)

    Can you explain what you're trying to accomplish? Are you trying to localize an Access app for Japan? VBA forms and controls employ IME but Access uses its own forms and controls so I don't think you can graft that on even if you reference the Word object library. You can test it for yourself by setting a reference to the Word library but any IME functions would be available only in code and not from the interface.
    Charlotte

  3. #3
    2 Star Lounger
    Join Date
    Feb 2002
    Posts
    155
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Using Word 9.0 object library (A2K)

    My requirement is very "simple". I want to set up a textbox in Access whereby when it is in focus, the IME is automatically turned on for input of East Asian characters (names of customers in Chinese), and when it loses its focus, the IME is disabled, and normal input in English is enabled. I read that MSO 2K understands unicode, I thought it is a matter of tweaking before one can input East Asian characters in its testbox. Thanks for your reply.

  4. #4
    Super Moderator
    Join Date
    Dec 2000
    Location
    Renton, Washington, USA
    Posts
    12,560
    Thanks
    0
    Thanked 4 Times in 4 Posts

    Re: Using Word 9.0 object library (A2K)

    "I read that MSO 2K understands unicode" wher did you read this?

    Now running HP Pavilion a6528p, with Win7 64 Bit OS.

  5. #5
    Silver Lounger
    Join Date
    Jan 2001
    Location
    Indianapolis, Indiana, USA
    Posts
    1,862
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Using Word 9.0 object library (A2K)

    FYI: In just over 24 hours I will have either an answer about this or I'll be scratching my head.

    I have an Access/SQL Server/Web application that will support 6 languages (English, Spanish, French, German, Chinese, and Japanese). I'm getting the first of the Chinese and Japnese translations in tomorrow so I'll find out just how to handle them in both Access/SQL Server and Internet Explorer. Although I have and use Office XP, my clients will be running the DB FE in Access2K.

    Wish me luck! <img src=/S/crossfingers.gif border=0 alt=crossfingers width=17 height=16>

    I'll post anything I find out in the process.

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Using Word 9.0 object library (A2K)

    Unfortunately it is not a matter of tweaking - first you need to install the correct IME for the version of Office that you are using. But in Office2K I don't believe you can really manipulate the language settings in VBA, which is what you would need to do. Office XP is more robust in this area, but still not a trivial exercise. You can create tables in Access Projects that store unicode characters, so in that sense I guess it is "unicode aware" but I don't believe you can do so in a Jet based database. I have had very little experience working with IMEs, so perhaps someone with more experience can comment further.

    <font color=blue>Edited by WendellB at 09:36 12-Sep-02</font color=blue>
    I should know better than to post things at ridiculous hours! The Jet version mdb file can also store Unicode characters - it does have a compression feature that only takes one byte per character for Text and Memo and Hyperlink fields if the first byte of a character is 0. Anyhow, I was wrong <img src=/S/exclamation.gif border=0 alt=exclamation width=15 height=15> <img src=/S/blush.gif border=0 alt=blush width=15 height=15> And it sounds like MarkJ may have an answer for you shortly.
    Wendell

  7. #7
    2 Star Lounger
    Join Date
    Feb 2002
    Posts
    155
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Using Word 9.0 object library (A2K)

    I can't recall where did I read this, or if what I read was meant for A2K or A2002. But I remembered reading that internally VBA represents every string in Unicode format, and has to convert the string to ANSI if Unicode isn't used. That caused me make the statement that MSO 2K can understand Unicode.

  8. #8
    Silver Lounger
    Join Date
    Jan 2001
    Location
    Indianapolis, Indiana, USA
    Posts
    1,862
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Using Word 9.0 object library (A2K)

    Partial News Update: I have tested Access 2000 (ADP with SQL Server back-end) and it DOES display Japanese characters with nothing beyond the default settings. The back-end data type is nvarchar.

    I'll work more with copy/paste from Word and Excel after a meeting tomorrow.

    Hope this update helps.... Stay tuned more.

  9. #9
    Silver Lounger
    Join Date
    Jan 2001
    Location
    Indianapolis, Indiana, USA
    Posts
    1,862
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Using Word 9.0 object library (A2K)

    Please forgive my late reply. My meeting last Friday did not give me much information regarding your problem. The only purpose was for me to present the English version of our Multilingual survey to the Chinese and Japanese translators.

    I have, however, learned how to read the Unicode characters from the SQL Server (7) database and present them in the appropriate language using ASP. Simply set your charset to UTF-8 and CodePage=65001....Voila! Works like a charm!

    Unfortunatley, I won't be doing any of the multilingual entry so I can not help with the IME issue. In my research on this issue I discovered a Language pack for OfficeXP that I have not seen before. Maybe there could be a newer language pack for Office 2000 that is new since you last looked? (just a long shot)

    Good luck!

  10. #10
    2 Star Lounger
    Join Date
    Feb 2002
    Posts
    155
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Using Word 9.0 object library (A2K)

    I think Charlotte is right - there is no way to make A2K forms IME-aware. Microsoft had only in mind to make IME a word-processing adjunct to Word for East Asian Language input and making A2K forms respond to IME was just too much trouble.

    I manage to find a convoluted solution to my own problem - input Chinese characters in English A2K forms. I used a Chinese front processors called Chinese Star 2001 (which is compatible with MS Office 2K) made by a company in China and marketed by SunTendy America Inc. Here are the procedures I used for those who are interested:

    (1) Run Chinese Star 2001 (CStar) first before A2K.

    (2) Start A2K and activate a form in design view. In the properties pop-up of the control boxes, an additional property called IME Mode will be inserted. The IME mode has three options : No Control, IME ON, IME OFF. Just leave the property with the default option - No Control. I suspect the IME on/off properties can be used in VBA codes. But since CStar has to be in memory before Chinese characters can be entered, I see no necessity to incorporate it in codes. More importantly, incorporating these properties in codes will halt A2K when CStar isn't running in the background.

    (3) Since I need to input Chinese names, I use a textbox to get user's input. CStar comes with many nice fonts which are not displayable once CStar is exited. Hence I don't use any of the CStar fonts supplied. Instead I choose the MS Song font (mssong.tff) by Microsoft (used by IE5 to display web sites using Simplified Chinese), which supports code page 936 : Simplified Chinese characters for PRC & Singapore, and which is displayable by CStar too. In this way, I can view Chinese characters together with other English input in the same A2K form without CStar. Note that CStar is still needed for Chinese characters input.

    Any caveat? So far there is one. If CStar is running and a controlbox with date input is edited, it will automatically be displayed in the traditional yy/mm/dd Chinese calendar format. However, if no editing is done or if CStar isn't running, the date format displayed follows the input mask or the format() in codes. I wonder if anyone has any idea how I can make the displayed date different from the yy/mm/dd format forced upon the user by CStar.

    I understand there are many other Chinese/Japanese/Korean (CJK) front processors available, like UnionWay and TwinBridge (by US companies), and NJStar (by an Australian company). I have only experimented only with CStar 2001 and it fulfills my need, albeit in a round-about way.

    My sincere thanks to Charlotte, WendelB and MarkJ for giving me pointers in searching for a solution to my problem.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •