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



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

Translating a mobile application

  • Filter
  • Time
  • Show
Clear All
new posts

  • Translating a mobile application


    I'm working on translating a mobile application. I've watched the 4 or 5 AA videos that I could find on the <a5:t> text dictionary functionality. I've created a local table with my key, language, and text columns. I'm stuck trying to get AA to use that local table. When in the "Web Project Properties" window I cannot figure out how to build the "Text Dictionary Table Settings" Connection String to use that local table.



  • #2
    Re: Translating a mobile application

    If your text dictionary table is in the same database as the rest of your project, then the connection string is simply:


    where "conn" is the name of your usual connection string

    Is that what you need to know?

    And re-reading your post, you keep referring to "local table". The table needs to be in the same database that the rest of your system uses.


    • #3
      Re: Translating a mobile application

      Some quick clarifications:

      1. I've created a table within my applications Control Panel to use for translation in my mobile application. This table has 3 columns (Key, Language, Data). I believe that this is an internal table to my project as it resides within my project's Control Panel. This is a .dbf table.

      2. When I go to my Web Project Properties and try to enter in the connection string I have to click the "..." to bring up the Define Text Dictionary Table screen. And while on that screen I cannot figure out what to define the Connection String as that will reference my internal table. Using your suggestion of ::Name::conn I've tried replacing "conn" with everything that I could think of, but nothing is working. Any suggestions?

      translation table.jpg

      Text Dictionary Connection String.jpg


      • #4
        Re: Translating a mobile application

        Look a little more at the dropdown for the "Table Type" in the Table Definition. I don't think you can use a DBF as a Text Dictionary table. It appears you can only use this feature with SQL tables.


        • #5
          Re: Translating a mobile application

          Good point Steve.

          Follow up question: Is it possible to deploy and access a SQL type database as part of a mobile application? I need to be able to access translation strings while offline. The videos that I've watched make it sound like you can deploy a dbf database with the mobile application.




          • #6
            Re: Translating a mobile application

            You can have a hybrid app that uses both DBF and SQL. But if you're already setting up SQL for part of it, why not just do all of it that way?

            I see you're new here (Welcome!) and wonder if some additional understanding is needed: Keep in mind that tables still reside on your server and the application needs to get to them at least once in a while because that's where the data's stored --- on your server, not the mobile device itself (yes, there are lots of exceptions to this with offline storage, localstorage, etc. but trying to stay with the basics here).

            Hope this helps a bit.


            • #7
              Re: Translating a mobile application

              Thanks for the welcome. Yes quite new with Alpha. If the text dictionary functionality requires a SQL connection, can I create a SQL database and have it accessed locally from my mobile app when I'm offline? Is this the "offline storage" that you mentioned in your reply? Thanks, Jason


              • #8
                Re: Translating a mobile application

                No, not quite. I think you need a better understanding of how a web application works. I will not attempt a full tutorial here, but basically:

                First, you need a web server. This server has, or has access to, the SQL database and/or in your case the DBF database -- in short, the database.

                The mobile device basically uses a browser to request pages from the web server. If the web server needs one of the pages you designed, it, of course, has it. If it needs data as part of that page, it of course goes to the SQL server. To emphasize, the data server and the web server are NOT on any local device. They're at your ISP, cloud service or whatever you choose to host the web server and database server.

                Mobile devices are not the web server. Mobile devices are not the data server. Mobile devices ARE the client.

                Now, there are advanced things you can do use clients as their local data sources (not server - source) but this is well beyond anything you might want to try soon. You need to get the basics in hand first.

                The way the Text Dictionary works is that the web server, as it's creating pages, sees things like <font> tags etc. and knows what to do with them to present the correct output to the client. The same goes with the <a5:t> tag -- the Alpha web server (and only the Alpha web server) knows what to do with these <a5:t> tags, and that is, to perform the desired query to the text dictionary table and provide the correct output to the client.

                Maybe others here have links to suggest about how a web application works, but you want to start with some basics and build from there.


                • #9
                  Re: Translating a mobile application

                  Steve, thanks for the insight. Learning more and more about AA. But also have a general understanding of the concepts that you talked about.

                  For an offline mobile AA application is there a recommended translation approach?

                  Thanks, Jason