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

calculate age from 2 separate tables?

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

  • calculate age from 2 separate tables?

    Searched the forums, help file and tinkered around with this, and I don't know how to do it.
    Table 1: Patient (Pt_t); Fields include:
    Pt_Id (numeric, primary key), pt name, DOB (date field), SS#, etc.
    Table 2 Patient visit (pt_vst_t); for any one patient there will be multiple visits to the office;
    Fields include:
    Pt_vst_id, Pt_Id (numeric, foreign key), Pt_Vst_Tm (time field instead of date field b/c patient may be seen more than one time in a day; e.g., seen in office in AM, comes back in PM b/c problem)
    The 2 tables are joined in a set (pt_vst_s) by the Pt_Id field with the Pt_t table being the parent table and the Pt_vst_t table being the child table.
    I wanted to add an age field (age at time of visit) to the pt_vst_t table but can't seem to do it.
    I added a field to the pt_vst_t called Pt_age making it a numeric field with width of 3; I then went to field rules -> field types, chose calculated, -> expression builder and entered age(); the field that it needs is the DOB from the Pt_t table which is not a choice;
    How do I get this to work? Thanks

  • #2
    Re: calculate age from 2 separate tables?

    When using a set fields from both tables are available for forms, reports, etc. Not sure why you feel the need to store that info in a table. You can use a lookup() to the child field value in your table calculated field if you must store it.
    There can be only one.

    Comment


    • #3
      Re: calculate age from 2 separate tables?

      Stan,
      Thanks for your reply.
      I added a calculated field to the form for the age. In the expression builder I entered age(dob,Pt_Vst_T->Pt_Vst_Tm) but it won't work with a time field. Able to get that to work when the field is set up as date type but not for time type. I guess that I could have a date field and a short time field for the office encounter "time-stamp" and then have the expression as
      age(dob,pt_visit_dt) but that would add an extra data entry item (short time) for the user and not be as "clean".
      Again, the patient occsasionally might be seen twice in one day, hence a time type field instead of just a date.
      Any different suggestions? Thanks.

      Comment


      • #4
        Re: calculate age from 2 separate tables?

        Originally posted by dlazenby View Post
        In the expression builder I entered age(dob,Pt_Vst_T->Pt_Vst_Tm) but it won't work with a time field.
        There are all sorts of date-time-shorttime conversion functions available.Perhaps you can find one that will let you derive the date from the visit time.
        There can be only one.

        Comment


        • #5
          Re: calculate age from 2 separate tables?

          Stan,
          Thanks for your help. I'll try some of those conversions.

          Comment

          Working...
          X