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

Seems Simple Enough

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

    Seems Simple Enough

    Hey there,
    This seems simple enough but I seem to be having a brain fade or something. In my table I have a field named "Date_in" which signifies when a file came in. I also have a field, "Date_Comp" which is filled in when a task has been completed for that file. What I'm trying to do is put together a report to show files that are 30 days or more older than the "Date_In" and the "Date_Comp" is blank. Now the code for the "Date_Comp" blank is easy enough but I just can't seem to figure out how to show the files that are 30 days or more older than the date in.

    For example, I thought maybe running a query for a range of dates in first and then querying those records for the ones that are still open and 30 days or more older than the "Date_in". Technically I shouldn't have to run 2 separate queries but I'm stumped as to how to get the records I need. If I use some thing like" Date_in >= Date_in + 30" it will look for specific dates in the "Date_In" field that meet that requirement, but if I have a set of records called up, let's say for November 2016, it will look for a "Date_in" of December 2 and up in the "Date_In" field. It obviously wouldn't find any because the current queried records are from November only. I can't call them up by the "Date_Comp" field being filled because there may be some where that field is actually not blank but the file is still not complete for other reasons. I can add those parameters to the query once I understand how to do it. I know this has something to do with aging but not sure how to approach it.

    Hope this makes some sense. Thanks for taking a look. Oh, I will be gone from the office until Monday (11/30/2017).

    Thanks,

    Scott

    #2
    Re: Seems Simple Enough

    Hi Scott,
    You didn't say how you want to display the query result - in a form or a report? However the simplest way is perhaps to add a numeric calc field to your table with this expression:

    days_exp = IF(date_comp <> {}, date_comp-date_in, 0)

    Now you can use this as your query filter: days_exp >= 30
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #3
      Re: Seems Simple Enough

      i think that days any job open is from that day the report is run
      for example if date_in was 12/01/2016 then when the report is run the job is open for 1/27/2017 - 12/01/2016, 57 days
      so i would design the report and then go to select records and fill in the filter

      Date_In < (Date() - 30) .AND. Date_Comp = {}
      or
      date()-Date_in > 30 .AND. Date_Comp = {}

      that should do it, i think.

      edit: it will be good if you post what backend db you are using, this reply assumes that dbf is being used. the query will change if it were sql variant.
      Last edited by GGandhi; 01-28-2017, 10:53 AM.
      thanks for reading

      gandhi

      version 11 3381 - 4096
      mysql backend
      http://www.alphawebprogramming.blogspot.com
      [email protected]
      Skype:[email protected]
      1 914 924 5171

      Comment


        #4
        Re: Seems Simple Enough

        Thanks guys, both are great approaches. For some reason I just could not wrap my head around it....lol. And Govindan, I am using A5 v11 only and no sql. I will be taking the results and exporting certain fields to produce an excel report that will be sent to one of our clients that are requesting which jobs are out past 30 days. I would prefer just to produce a report, but they like data that can be manipulated the way they want. Thanks so much for the ideas gentlemen, they are greatly appreciated!

        Scott

        Comment

        Working...
        X