none
ASP call power builder to replace Chinese characters in word documents on windows 2003 RRS feed

  • Question

  • a ASP page calls power builder to replace Chinese characters in word documents on windows 2003. However, the replaced word become unreadable '2015¦~8¤ë'. 

    I tried to use the following methods:
    converted the webpage program from acsii to utf-8 and unicode seperately
    converted the field varchar to nvarchar in database store
    installed the updated fonts

    But the issue still happen and cannot be fixed.

    Could you help? Great thanks

    Tuesday, August 4, 2015 7:45 AM

Answers

  • the locale is changed; the issue is also solved.
    • Marked as answer by alex121 Tuesday, August 4, 2015 9:11 AM
    Tuesday, August 4, 2015 9:11 AM
  • Hello Alex,

    Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.

    If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution. Read more about that in the Considerations for server-side Automation of Office article.

    You may consider using any third-party components designed for the server-side execution. Or, if you deal only with open MXL documents, you may consider using the Open XML SDK, see Welcome to the Open XML SDK 2.5 for Office .

    • Marked as answer by alex121 Tuesday, August 4, 2015 9:24 AM
    Tuesday, August 4, 2015 9:13 AM

All replies

  • the locale is changed; the issue is also solved.
    • Marked as answer by alex121 Tuesday, August 4, 2015 9:11 AM
    Tuesday, August 4, 2015 9:11 AM
  • Hello Alex,

    Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.

    If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution. Read more about that in the Considerations for server-side Automation of Office article.

    You may consider using any third-party components designed for the server-side execution. Or, if you deal only with open MXL documents, you may consider using the Open XML SDK, see Welcome to the Open XML SDK 2.5 for Office .

    • Marked as answer by alex121 Tuesday, August 4, 2015 9:24 AM
    Tuesday, August 4, 2015 9:13 AM
  • many thanks!!
    Tuesday, August 4, 2015 9:24 AM