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

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

Managing a Transaction Table

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

  • sollasollew
    replied
    Re: Managing a Transaction Table

    Thanks much. Filter on the lookup it is. I will explore the help on this topic. I don't believe Access, where I have some familiarity, can do this. At least not very easily.

    Eric

    Leave a comment:


  • sollasollew
    replied
    Re: Managing a Transaction Table

    My thinking was the present status of something is, for all intents and purposes, the same as the last change. In this case, we need to record changes in status. The current would be the status at the most recent date.

    Erc

    Leave a comment:


  • sollasollew
    replied
    Re: Managing a Transaction Table

    My thinking was the present status of something is, for all intents and purposes, the same as the last change. In this case, we need to record changes in status. The current would be the status at the most recent date.

    Eric

    Leave a comment:


  • Tom Cone Jr
    replied
    Re: Managing a Transaction Table

    Eric, there's a difference between recording the present status of something, and recording the changes to that status over time. Which are you asking about here?

    Leave a comment:


  • Keith Hubert
    replied
    Re: Managing a Transaction Table

    Hi Eric,

    Welcome to the world of Alpha.

    You have asked a number of questions here, the best thing to remember here is that it is easier to reply to single questions, as there could be a number of answers and the topic needs to remain coherent.
    can you get the values in drop down 2 to change, based on the values in drop down 1?
    The anser is Yes; This would be done with a filter in the lookup.
    Question is, each assessment has a different range of possible scores. The viral load score might vary between 0 and 1, whereas the psychiatric measure might vary between 10 and 50. It would be good to be able to trap for out-of-range entries but the range will change for each type of assessment. Any clues?
    Conditional objects come to mind, where you would have different layers with different score methods for different conditions.
    does this approach, using a small number of transaction tables make sense?
    Not quite, but you might need a number of small tables for the lookups.
    will this work as well with a deskop versus and online application
    Very simply, Yes, but the setup for web pages is not the same as desktop.

    Leave a comment:


  • sollasollew
    started a topic Managing a Transaction Table

    Managing a Transaction Table

    Spent some quality time learning a bit about Alpha5 yesterday. So far, so good. I would like to create a transaction table that records status changes for clients in an HIV/AIDS program. Each client will have several things he/she can have a status change about.

    I would like to create a single table for all of this. After selecting a client, users would select the status being changed from a drop down. Then, and here's the rub, only the values relevant for the status being changed, would be available. For example, if the client had a new housing status, the worker would select 'New Housing Status' from the 'Status Type' field and the 'New Status' field would include only things like "Became homeless", "Living in shelter", etc.

    I realize first that theses choices would have to be fed from a table, this is preferred for a number of reasons. Question is, can you get the values in drop down 2 to change, based on the values in drop down 1? Is there an example of this in the help or in AlphaSports?

    On another note, there are also certain numerical scores that will change for each client. Viral load is one, score on a psychiatric assessment is another. I can provide a separate score table and form set up to handle a numerical value. Question is, each assessment has a different range of possible scores. The viral load score might vary between 0 and 1, whereas the psychiatric measure might vary between 10 and 50. It would be good to be able to trap for out-of-range entries but the range will change for each type of assessment. Any clues?

    Finally, does this approach, using a small number of transaction tables make sense? Finally, finally, will this work as well with a deskop versus and online application.

    Thanks much.
Working...
X