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

I am missing something

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

    #31
    RE: I am missing something

    Uh OH

    Comment


      #32
      RE: I am missing something

      Open the Expressions Functions Reference book to page 18 or search for between_date().

      kenn
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment


        #33
        RE: I am missing something

        efs,

        1. Click on the Report tab of the control panel
        2. Open your report in design mode
        3. Click the Report menu
        4. Select Properties
        5. Select Detail properties
        6. Paste this code in the filter expression box...

        between_date(date_field,Var-"askD_Start,Var-"askD_End)

        As Robert Emery points out, replace date_field with the field name which contains your date field. However, if you are using 2 date fields such as Begin_Date and End_Date, that changes things. In that case, ope the expression filter's expression builder and use the expression genie. Be sure to read all the choices as ther is one that will work very well.

        kenn
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment


          #34
          RE: I am missing something

          Hi Kenn,

          I have done that several times without success. Stan pointed out that my date field needed quotes around it if I use between_date (which I had been using)as opposed to between. Hence I used;

          between_date("received-"rcv_food_dt",starting_date,ending_date).
          It just will not work in this case.

          The following does work;
          between(received-"rcv_food_dt,starting_date,ending_date)

          Go figure,
          Ed

          Comment


            #35
            RE: I am missing something

            Edward,

            There is one other difference of the two functions which Stan didn't make note of. Namely, the return values are different.

            If you need a logical value as a return type, use BETWEEN() which seems to be working for you:

            ?between(date(),{03/01/04},{10/01/04})
            = .T.

            If you want a string value returned which can be used as a filter expression, use BETWEEN_DATE():

            dim dt as D
            dt=date()
            ?between_date("dt",{03/01/04},{10/01/04})
            = "between(dt,{03/01/2004},{10/01/2004})"

            As you see from this, BETWEEN_DATE() utilizes the BETWEEN() function after replacing the field name (or variable name as in this example) with it's date value.

            Personally, I avoid BETWEEN_DATE() altogether since its advantages and usefulness are minimal when compared to the confusion it brings.

            Steve

            Comment


              #36
              RE: I am missing something

              BETWEEN_DATE() returns a character string that is a quoted filter expression that uses two date values. This function is only useful in Xbasic scripts. .......

              Frequently in Xbasic scripts, you need to specify a filter expression in quotes. It can get quite tricky to do this if your Low_Value and High_Value values are stored in variables. ..........


              so you can simply use

              query.filter = between_date("date", first, last)

              instead of something like

              query.filter = "between(date,{"+dtoc(first)+"},{"+dtoc(last)+"})"
              There can be only one.

              Comment


                #37
                RE: I am missing something

                Hi Steve,

                Thank you for the explanation. I agree that between_date() is a bit confusing and probably never needed. Rest assured that I'll probably never use it again.

                Thank you,
                Ed

                Comment


                  #38
                  RE: I am missing something

                  Didn't mean to step on your answer, took me a while to construct my reply.
                  There can be only one.

                  Comment


                    #39
                    RE: I am missing something

                    Hi Stan,

                    Thank you for the reply. It does appear that it's usefulness is limited.
                    Thanks again,
                    Ed

                    Comment


                      #40
                      RE: I am missing something

                      That's OK, Stan. Moreover, you gave a better explanation of the real uses of BETWEEN_DATE().

                      Just to add a note on the "confusion" aspect of this function, most all functions are named so that their use or meaning is exactly what you would expect from the English words which comprise the name. For instance, ISDATE() does indeed return a logical value depending on whether a supplied date is valid. If the funtion in question were named, say, BETWEEN_DATE_EXPN() the confusion would be reduced since the function name would indicate that an expression (character type) is returned. For most people (as indicated earlier in this thread) the name "BETWEEN_DATE" intuitively indicates a logical return value same as "BETWEEN".

                      It is for this reason that I believe my source code "reads" better to fellow developers if I use the BETWEEN() function and avoid the BETWEEN_DATE() function. My 2 cents.

                      Steve

                      Comment

                      Working...
                      X