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

Age from DOB - but 2 different tables

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

    Age from DOB - but 2 different tables

    I have two tables connected in my grid which is based on a view. One table (called "Admin") lists the Date, Time, Location, etc. of a particular incident. The second table (called "Persons") lists all of the people associated with the incident.

    Within the Persons table is a field for the person's DOB and AGE, but the AGE field is just a label, as I was originally calculating the AGE through a field rule on the back end, by using the AGE(DOB) formula. Then I realized I was doing this wrong, because anytime I had to recalculate the records, the person's age was changing, as it was based on the formula of subtracting the DOB from the current system date.

    What I *should* have been doing, was calculating the person's age based on subtracting the DOB from the "Date of the Incident," (actually called "Daterep") so it would never change. That way, if someone prints an old report, and a person was 17 at the time of the incident, the person will still show up as 17 in the report, even though he may now be 21 or older.

    But here's my problem, the "Date of Incident" (Daterep) is in the Admin table, and I can't see how to make that field rule work in the back end with the "Daterep" coming from a different table.

    I can calculate it on the web screen using a calculated query definition, but I'm not sure how to get the actual age to submit to the AGE field so it will stay there. (I need the age data in the persons table because it is used to determine other conditional fields in reports, etc., so just showing it on the web screen is not enough.)
    Sergeant Richard Hartnett
    Hyattsville City Police Department
    Maryland

    #2
    Re: Age from DOB - but 2 different tables

    You could create an expression in field rules as a Default (not a calc). Or use a calc but include code to only render a calculation if the age field is presently blank. In either case the Age will not show up in the grid until you submit the data.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Age from DOB - but 2 different tables

      Thanks for the quick resonse Steve, but I'm still confused.

      Using field rules it looks like the correct expression to figure an age between the person's DOB and (in my case) the Date of the Incident (Daterep) would be:

      age(DOB,Daterep)

      But since the "Daterep" field is in a different table, how do I get in into my expression? It won't show up in the list of available fields because the "Persons" table doesn't contain that field.
      Sergeant Richard Hartnett
      Hyattsville City Police Department
      Maryland

      Comment


        #4
        Re: Age from DOB - but 2 different tables

        find lookupd() in the help file.
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment


          #5
          Re: Age from DOB - but 2 different tables

          Missed that pont - is there some relationship between Persons and Incident, IncidentID perhaps, then something like:

          age(DOB,lookupd("F", IncidentID,"Daterep", [pathalias.adb_path]\incident.dbf","IncidentID"))

          EDIT: oops - as Dave said, above.
          Steve Wood
          See my profile on IADN

          Comment


            #6
            Re: Age from DOB - but 2 different tables

            My "Incident" table is called "Incadmin_ncpd" and the relationship I guess would be my field called "LinkingKey," so I used the following expression based on your example:

            age(DOB,lookupd("F", Linkingkey,"Daterep", [pathalias.adb_path]\Incadmin_ncpd.dbf","Linkingkey"))

            but it is telling me that the expression is invalid.
            Sergeant Richard Hartnett
            Hyattsville City Police Department
            Maryland

            Comment


              #7
              Re: Age from DOB - but 2 different tables

              rich,
              look up lookupd() in the help file. It may make more sense to you.

              it only gets the date from wherever you have it stored.

              then you need to do the math.
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment


                #8
                Re: Age from DOB - but 2 different tables

                For what it's worth, when I use a calculated field that I want to only have calculated once I only do it IF the the field to be calulated is null or = "".

                IF (calcfield = "", the calcualtion happens, calcfield), so if the calcfield has something in it then calculate to put the same thing back into it and save it.

                Hope that helps.
                Insanity: doing the same thing over and over again and expecting different results.
                Albert Einstein, (attributed)
                US (German-born) physicist (1879 - 1955)

                Comment


                  #9
                  Re: Age from DOB - but 2 different tables

                  That does help Pete, thanks.
                  Sergeant Richard Hartnett
                  Hyattsville City Police Department
                  Maryland

                  Comment

                  Working...
                  X