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

Column title

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

  • Column title

    In A5V5 I have a form with two embedded browses. When I change a column title in on of them to a word with the swedish extended character - (A with two dots) - I get an error "field is not valid". Changing to another swedish character - (O with two dots)- it works as it should. I am aware that extended characters should not be used in field and table names, but I thought I should be able to use swedish in the forms. Any suggestions, aside from using english all through of course.

    Thanks in advance

    Jan

  • #2
    RE: Column title

    Jan,

    I'm not clear when you get the error. Are you unable to do the change and save the form? Or is is when you try to refer to field? If the latter, the error would be due to the fact that the "field" of a browse is actually the column title so you would have to change the field reference in the code to include the accented character.

    One way to do this would be to include a function to remove the accents in the code which refers to the field.

    Search on "No_accents" (or perhaps "no accents").

    Bill
    Bill Hanigsberg

    Comment


    • #3
      RE: Column title

      Here's the reference:

      http://msgboard.alphasoftware.com/alphaphorum/read.php3?sortby=lastreply&direction=desc&num=11&id=36251&thread=35905

      You will have to amend the function to include the characters relevent to your user base.

      Bill
      Bill Hanigsberg

      Comment


      • #4
        RE: Column title

        Bill,
        I change the title of the column in Design and save it. It is when I try to View the form that the error occurs.
        Jan

        Comment


        • #5
          RE: Column title

          Jan,

          Are you able to edit the title, save and view the form when you do NOT use an accented character in the new title?

          Bill
          Bill Hanigsberg

          Comment


          • #6
            RE: Column title

            Bill,

            yes and it is only the A with dots that makes trouble, not the O. I am sorry to say that I do not understand: "you would have to change the field reference in the code to include the accented character".
            Thanks for our help

            Jan

            Comment


            • #7
              RE: Column title

              If you write xbasic which refers to a field in an embedded browse you must refer to the column title in the browse rather than the field name even though by default they are the same. However, it does not appear that this is your problem.

              I have been having machine problems in the last 2 days. If I can find a moment I will do some experiments with your issue. You may also want to post an example of the problem.

              Bill
              Bill Hanigsberg

              Comment


              • #8
                RE: Column title

                Jan,

                I took a form based on a simple table and added an embedded browse based on the same table. I then renamed the "firstname" column to "Firstname". I made "" by typing alt_233 and I copied "" from the windows character map utility.

                The form saved and displayed without issue.

                I suggest you do a similar experiment just to be sure nothing else in your application is the source of your issue. If you still cannot succeed, you should post an example for others to run on their machines.

                Based on my experience the problem could be due to pageframe or some other setup parameter. Where I work I discovered that the French-language setup on some machines and *not* the French characters would cause problems.

                Bill
                Bill Hanigsberg

                Comment


                • #9
                  RE: Column title

                  Wrong letter:

                  I just tried "" and there were no problems. ( from the character map.)
                  Bill Hanigsberg

                  Comment


                  • #10
                    RE: Column title

                    Bill,

                    Before I wrote my first message I got the same error repeatedly, no matter what I tried. Now suddenly, without havning done anything actually, both , and works in titles both for fields and embedded browses. ?????? Thank you very much for your help. I love the feeling that should I have a problem there is always someone out there who knows and takes time to help.

                    Jan

                    Comment

                    Working...
                    X