Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Unicode support and/or trial version

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Unicode support and/or trial version

    I would like to know if version 5 supports Unicode text fields. I have an application that stores and prints the inventory name in both English and Chinese. It works fine under Windows 98, but does not work under Windows 2000 or XP because they use Unicode character sets. The client now wants to buy a new computer and upgrade the system to run under Windows XP.

    Does version 5 support Unicode text correctly?

    Does Alpha plan to post a 30-day trial version on the web so I can do a Unicode compability test?

    #2
    RE: Unicode support and/or trial version

    I am sorry to report that we do not yet support UNICODE. We won't be able to support unicode until we get away from the legacy DBF backend, whose file format is single byte ascii (we would need to break way to much code to support unicode).

    I do intend to look at the possibility of supporting unicode when we move to the client/server version, but again, this will depend on the limitations of the back-end.
    So, no promises on being able to ship a unicode version of 6.0.

    Comment


      #3
      RE: Unicode support and/or trial version

      The oem_to_ansi function has helped me solve similar issues.

      Bill
      Bill Hanigsberg

      Comment


        #4
        RE: Unicode support and/or trial version

        I have apps in v4.5 that stores, index, search and in general most of operations in Korean characters without any problems. I can even query using expression builder in report layout. I have tried the apps on Win98 SE and WinME (in Korean and English OS) and English XP with Asian characters installed.

        In v5, however, I can't even enter into a text field let alone store or index. I don't know what the difference is between the two versions but I can only utilize v4.5 for apps with Korean character usage.

        Eugene

        Comment


          #5
          RE: Unicode support and/or trial version

          Bill,

          can you further elaborate on the issue (perhaps even with a simple example). Thanks.

          Eugene

          Comment


            #6
            RE: Unicode support and/or trial version

            Eugene,

            I don't want to over promise as I have not experimented with oriental characters. My experience has been with the accented characters such as "�" in various European languages.

            As I understand it these are part of the extended ascii character set and are mapped diffently in different code pages of which (believe it or not)French as three which leads to screwups.

            This solves the problem:
            output_str=oem_to_ansi(input_string)

            This is from the xbasic reference:
            -------------
            oem_to_ansi()
            Syntax:
            Result String = oem_to_ansi(Source Buffer Name, Number of
            Characters)
            Description:
            Converts the specified Number of Characters in the Source Buffer from the
            OEM (DOS) character set to the ANSI (Windows) character set, and returns the
            result in Result String.
            See Also:
            ansi_to_oem()
            -------------

            Since you have it, why not give it a try.

            Bill
            Bill Hanigsberg

            Comment

            Working...
            X