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

Crashing A5 when designing report?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Crashing A5 when designing report?


    Two disclaimers before I get to the meat of the problem:

    1) Despite the fact that this says "Rose Edwards", I am Greg McMullan - I am temping in Rose's position for the time being.

    2) I have only recently started using Alpha 5, though I've been programming for many years, and spent about ten years working with the Progress database in my previous job. I have not yet gotten the hang of all of Alpha's style, so feel free to point out ways where I am doing things the hard way.

    My boss has encountered an oddity in running a report, which seems to have led me to a more serious underlying problem. She modified a report that had been running before I started in this job by adding a calculated field to concatenate the First and Last names of a person. The field she called "NameF", and it's expression is "alltrim(Personne->First)+" "+alltrim(Personne->Last)". Personne->First and Personne->Last are character strings containing the first and last names of personnel. WHen she runs the report, the field shows up as "NameF", instead of people's names. When she previews the report, it also shows up as "NameF". If she goes into Design, and just looks at the properties of the field, then runs the report, it works as expected. I believe that this is a report-level calculated field, but I am not sure. This is Alpha 5 4.5, build 266, running on Windows 2000, from a directory on a Netware 5 server.

    *My* problem is that if I try to do anything with the field "namef" in an expression, even in a brand new report, as soon as I click on the field name in the expression builder, Alpha 5 crashes. Somehow, I think that this may indicate corruption somewhere, but I don't know enough about things Alpha to know where, or how to fix it yet. Any suggestions for what to do, or what to read to learn more would be greatly appreciated!



  • #2
    RE: Crashing A5 when designing report?


    the calculation looks okay. check the property of the NameF field in the report layout. It sounds like the field name was dragged to the report and not the field.

    you can delete the namef field first from the layout and then place it back in the report.

    i hope this helps.

    bob adler


    • #3
      RE: Crashing A5 when designing report?

      Any references to this field in other calculations must be in the form of


      you might check to see if it is used elsewhere.
      There can be only one.


      • #4
        RE: Crashing A5 when designing report?

        A5 will show the fieldname if the calculation has an error in it. Check for an error by bring up the expression and pressing the evaluate button. If some changes have been made, a character field may now be a numeric and cause a function to error out.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein