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

Getting DBMIN to ignore blank (null) dates?

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

  • Getting DBMIN to ignore blank (null) dates?

    I am attempting to retrieve the earliest date in a "maintenance due" field of a child table in a set (One to many relation). This seems to work perfectly using dbmin() as long as there are no blank dates in the child records.

    However, if one of the child records has a blank in that field, then the function dbmin returns a blank as the earliest value. I do not want to include blanks in this result, but rather return the earliest date that is not blank (unless of course all child records are blank).

    Does anyone know a way to restrict dbmin to not return a value of blank if there is at least one non-blank entry?

    I know that tablemin() has the ability to filter the records returned, but it returns the minimum for the entire table, not just the records connected to the parent.

    Thanks for any help/ideas/workarounds you may be able to offer.

  • #2
    Re: Getting DBMIN to ignore blank (null) dates?

    Try a variation of your current dbmin expression and use

    "if(trim(cdate(datefield))>"",datefield,{12/31/2099})"

    as the final parameter (lookup expression as C).
    There can be only one.

    Comment


    • #3
      Re: Getting DBMIN to ignore blank (null) dates?

      Thanks Stan,

      That is almost exactly what I need.

      Here is my calculated field:
      NextMainDue = dbmin("sequip1","Addressid",Id_S,"if(trim(cdate(Sequip1->Maintduedate))>'',Sequip1->Maintduedate,{12/31/2099})")

      This produces exactly what I need, except that if there are no dates at all in the child record, it shows as "12/31/2099".

      Any suggestions as to how to have it display a blank field instead of the "12/31/2099"? If I change the dbmin from {12/31/2099} to simply "", then the function seems to fail and returns nothing.

      Comment


      • #4
        Re: Getting DBMIN to ignore blank (null) dates?

        Define an intermediary result

        im_rslt = dbmin("sequip1","Addressid",Id_S,"if(trim(cdate(Sequip1->Maintduedate))>'',Sequip1->Maintduedate,{12/31/2099})")

        then

        NextMainDue = If(calc->im_rslt <> {12/31/2099},calc->im_rslt,{})

        Of course you could just collapse that to

        Code:
        NextMainDue = If(dbmin("sequip1","Addressid",Id_S,"if(trim(cdate(Sequip1->Maintduedate))>'',Sequip1->Maintduedate,{12/31/2099})") <> {12/31/2099},dbmin("sequip1","Addressid",Id_S,"if(trim(cdate(Sequip1->Maintduedate))>'',Sequip1->Maintduedate,{12/31/2099})") ,{})
        Last edited by Stan Mathews; 02-15-2010, 03:17 PM.
        There can be only one.

        Comment


        • #5
          Re: Getting DBMIN to ignore blank (null) dates?

          Thanks, Stan! Works exactly as I need now...

          I'm a little confused and would love to know why I couldn't simply substitute { } for {12/31/2099} in the first suggestion you made.

          I'm grateful to see it work right, but I'm one who always likes to know "Why?"

          Thanks again for the assistance!

          Comment


          • #6
            Re: Getting DBMIN to ignore blank (null) dates?

            Originally posted by gkpurcey View Post
            I'm a little confused and would love to know why I couldn't simply substitute { } for {12/31/2099} in the first suggestion you made.
            Substituting {} in the first suggestion would have gotten you back to where you started. The parameter as suggested "says"

            compute the minimum of Maintduedate (if it is greater than {}) and {12/31/2099}

            so if the date is blank ({}) we pretend it is {12/31/2099} and trick the dbmin() function into never considering it as the minimum so long as there are valid dates.

            If I change the dbmin from {12/31/2099} to simply "", then the function seems to fail and returns nothing.
            You can't use "" because that is not a date value and dbmin() can't use it for comparison.
            Last edited by Stan Mathews; 02-15-2010, 03:37 PM.
            There can be only one.

            Comment


            • #7
              Re: Getting DBMIN to ignore blank (null) dates?

              OK, that does make sense that the dbmin() function would require the last parameter to be of the same type as the column it's trying to evaluate.

              Thanks for the explanation.

              Comment

              Working...
              X