PPJ Manual
HomeCurrent IssuesDownloads
  • Welcome
  • Releases
    • PPJ 2023
  • PPJ 2023
  • PPJ Web API
  • PPJ Desktop API
  • Wisej.NET Documentation
  • General
    • Framework
      • Features
        • SAL and SQL Functions
        • Constants and Variables
        • SalContext
        • Visual Toolchest
        • XSal2
        • Reporting Support
        • LINQ Support
        • SalCompileAndEvaluate
        • Unicode Support
        • Startup Arguments
        • App.config
      • Data Types
        • Automatic Casts
        • Dynamic Arrays
      • Controls
        • ToolBar
        • TabControl
        • TableWindow
        • QuickObject
        • Ribbon Bar
        • NavigationBar
      • SQL Support
        • Configuration
        • ADO.NET Drivers
        • Bind and Into Variables
        • DBP Parameters
        • SqlContext
      • Extensions
        • Table Window
        • Unicode Support
        • Bug Fixes
        • Object Oriented Types
        • Custom Parsers
        • Named Properties
        • Microsoft Charts
        • Tabbed MDI
        • Watermark
        • HTML Rendering
      • Skins and Themes
        • Skin Files
        • Theme Files
        • Configuration
        • Skin Editor
        • Theme Builder
      • Tracing
        • Trace Viewer
        • Default Listeners
        • Tracing the Application
      • Spell Checker
        • Dictionaries
    • Ported Application
      • Project Structure
        • Late Bind Calls
        • Visual Styles
        • Unqualified References
        • Message Actions
        • When SQLError
        • Classes
      • Global Items
      • Forms
      • COM/ActiveX
      • Multiple Inheritance
      • Configuration Tool
      • Issues & Workarounds
    • Ported Reports
      • General
      • Crystal Reports
        • Structure
        • Unsupported Features
      • List & Label
        • Report Conversion
        • Structure
        • Document
        • Input Items
        • Passing Data
        • Unsupported Features
      • Reporting Services
        • Features
      • Stimulsoft
        • Break Groups
        • Fields
        • Formulas
        • Cache Mode
Powered by GitBook
On this page
  • UNICODE Database
  • UNICODE Files
  • UNICODE Externals

Was this helpful?

  1. General
  2. Framework
  3. Features

Unicode Support

PreviousSalCompileAndEvaluateNextStartup Arguments

Last updated 2 years ago

Was this helpful?

.NET strings and controls are all UNICODE. Therefore the ported application becomes UNICODE compliant without any modifications.

However, when external resources are involved, you may need to modify the application and/or the external resource to become UNICODE. Generally there are three external resources that are not UNICODE: Database, Files, and External functions.

UNICODE Database

If your database is not UNICODE, make sure that the <encoding> setting in the file is set to Ansi. On the contrary, if you have converted the database to UNICODE, or are connecting to a UNICODE database, make sure that the <encoding> setting for the UNICODE data source in sql.config is set to Unicode.

UNICODE Files

All file operations in SQLWindows/Team Developer are not UNICODE. If you want to open, read and write UNICODE files (or using other standard encodings), you can use the following additional flags with the SalFileOpen function: Sys.OF_Unicode, Sys.OF_UTF7, Sys.OF_UTF8.

UNICODE Externals

By default, when passing strings to an external interop call, .NET converts the string to ASCII. If you need to call external DLLs that expect a UNICODE string you need to add the CharSet=CharSet.Unicode attribute to the external declarations in the Ext class (or Externals for VB.NET) in the ported project.

sql.config