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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Field Rules questions

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Field Rules questions

    I'm new to Windows DB work and to Alpha5V5. Can anyone comment on the following?

    1) In Field Rules - Lookups: If creating a Simple List (instead of reading from another table), is there some way to apply an index or sequence the entries to the Simple List? Also, is there a recommended maximum of entries in such a format?

    2) Age calculation: In Field Rules - calculated field expression. I have a table in which the respective fields are named "DOB" for Date of Birth and "AGE" for current age. The Expression Builder displays N age (d dob [,d asofdate]). I have brought this up in the Expression Builder but can't get out of that screen because it is not acceptable to produce the calculation to produce the current age (i.e., current date - date of birth). What do I need to do to resolve this? Thanks.
    Tags: None
    #2
    RE: Field Rules questions

    Stanley,

    This is my opiinion so others may not agree in part or entirely.

    1. is there some way to apply an index or sequence the entries to the Simple List?

    Right click on the field, select Events and then go to the fields OnArrive or OnChange event, use action scripting to select the index. Then if the index needs to be cahanged back to a previous index, do the same with the OnDepart event. I've not tried it but that what's comes to mind. Others may have a better idea.

    Also, is there a recommended maximum of entries in such a format?

    How log a list do you want and more importantly, if the list must be edited, added to or deleted from on a somewhat regular basis, then a lookup table would probably be better, especially if a user must do the editing. I don't think the simple lookup list can be edited w/o going to the field rules.

    2. Try a search for current age or age, etc. I have a function for this; it's in A5v4 but should work in v5. There are several ways to do it and this has been mentioned before. I'll dig out my function when I get a chance in a little while.

    kenn

    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment

      #3
      RE: Field Rules questions

      1. The simple list is viewed in the same sequence that you enter the values when in the field rules.

      2. Since you only said "I have brought this up in the Expression Builder but ... it is not acceptable", I must assume you didn't modify the expression at all. You must replace the "D DOB" with the actual date date of birth or with a field/variable that contains the date of birth. Similarly, the age( bdatef ) will give the age as of 'today'.

      HOWEVER, if this calculation is used for a calculated field in a table, the age will ONLY change when some value in the table is changed. Therefore, it will not be accurate when viewing a record that hasn't been changed for 3 years! It would be much better to use a calculated field that is only attached to the specific form, report, or other layout that is in use - this way the calculated age will be up-to-date since it will be recalculated every time a new record is fetched..

      FWIW: You will get more, better, and faster responses in the future if you provide more details about the actual expression/issue you are having trouble with. Without any guidance we have no idea what is wrong and many users won't respond at all if the issue isn't clear. For example, how would you give an accurate response to: "Could you please tell me why my car wouldn't start this morning? I tried to start it just like the manual told me to."

      Comment

        #4
        RE: Field Rules questions

        Great suggestions! I'll take them into account and provide more specifics in any future questions (which I'm sure to have). I'm so new to the whole package, I don't have much of a feel for the context of the entire operation, but I'll try to become a quick study. Ah, details, details, details, but that's the name of the game.

        Comment

        Previous template Next
        Working...
        X