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

A4 system variables

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

  • A4 system variables

    in A4 you could use the system variable to determine what the mode of the user was in as below

    if(%SYS_USER_MODE="ENTER","do A","do B")

    is there a similar variable in A5 to determine the same thing??

    Also in A4 you could read the fields of a record into temp system variables by doing a lookup of that record as below

    {XLOOKUPR "equipmnt",VAL(%trec), %status}

    once the record was read, i could use the variable %equipmnt_trct_no to populate the data field.

    is there a way to do this in A5 now?? or do i have to explicitly read the record and set all the fields to defined variables i need to address before i use them??

    thank you for your help in advance.

  • #2
    RE: A4 system variables

    You need to look for the "TBL".MODE_GET() and LOOKUP() functions also TABLE.EXTERNAL_RECORD_CONTENT_FROM_KEY_GET() and TABLE.EXTERNAL_RECORD_CONTENT_GET()
    If you don't have the CHM help file you should get it. Also down load the PDF files and look at the functions & methods.pdf you'll find all of the functions from V4 and a lot more.

    Allen

    Comment


    • #3
      RE: A4 system variables

      Hello Don,

      I used the system variables of A4 all the time and when I began with A5 I went looking for their counterpart. I was sorely disappointed when I only found a couple in A5. But as I soon realized A5 has a whole different paradigm. In A5 we mainly use object methods, which are much richer and more plentiful.

      As Allen said, *.mode_get() is the way we find out what mode the user is in. You can also use mode_get() with the form with the following syntax:

      Parentform.mode_get()


      ""{XLOOKUPR "equipmnt",VAL(%trec), %status} ""

      The lookup functions in A5 are very similar to A4, you won’t have any trouble here.

      The transition takes a little work, but it is well worth it. A5 is a very powerful environment and is being extended faster than I can keep up with :-)

      Good luck,
      Jim

      Comment

      Working...
      X