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



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

XBASIC: SQL Argument for Date Range

  • Filter
  • Time
  • Show
Clear All
new posts

  • XBASIC: SQL Argument for Date Range


    I am trying to use args.set(argname, "blahblah") for some SQL work but I am not sure how I can use it to specify a date range.

    I want to be able to say args.set("startdate", "between 10-10-2020 and 10-20-2020") <-- just an example ... I know it isn't correct.

    Any tips? I checked documentation and searched forum but I'm not able to find anything related to this.

  • #2

    and then in where clause:

    WHERE date BETWEEN :vdate1 AND :vdate2
    Gary S. Traub, Ph.D.


    • #3
      Hi Doc, thanks! I feel so stupid - I'm not sure where my mind was when asking that.


      • #4

        No worries. I am sure we have all done that sort of thing. I know I have many times. Happy to be of help.
        Gary S. Traub, Ph.D.


        • #5
          Hey Doc, I have a follow up question...been stuck on this for a few days now and just lost.

          I have a form with some fields, lets say "nameFirst", "nameLast", and "State". The user can click a button and I am trying to generate a SELECT statement in XBASIC.

          i need to create a WHERE clause to include one or more of the above fields, ie SELECT * from table WHERE nameFirst = 'Chris' and nameLast = 'Doe'

          Or if they enter just a last name and state could be "....WHERE nameLast = 'Doe' and state = 'NJ'"

          On my actual form, there are numerous other fields. Any tips on how to generate the where clause to include or not include filled in fields? I did not want to do a ton of IF/THEN statements because then I need to add "and" between them etc.

          This is on a UX.



          • #6
            I approach these types of things with a select case statement.

            You can do this in 2 stages.

            Stage 1:
            cmd="SELECT * from table WHERE"

            case nameFirst > ""
            cmd=cmd+"nameFirst = "+ s_quote(nameFirst)
            add_and = .t.

            case nameLast > ""
            if add_and then
            cmd=cmd+" .and. "
            end if
            cmd=cmd+"nameLast = "+ s_quote(nameLast)
            add_and = .t.

            case State > ""
            if add_and then
            cmd=cmd+" .and. "
            end if
            cmd=cmd+"State = "+ s_quote(State)
            add_and = .t.

            end select

            Stage 2:

            From a list of fieldnames that you are going to select from, you can loop through them and build the code shown in stage 1.

            Then use evaluate_template() to execute that code.
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein



            • #7
              Thanks Al! I'll give this a shot. I appreciate it!


              • #8
                and just when you think all hope is gone, another option is provided.
                I think this does what you want. You can use the supplied UX to test the code, there is nothing really special.
                I did not include a lot of validating, just a basic proof of concept type thing.
                Let me know if you have any questions.

                dim myfilter as c
                dim tracker as n = 0
                dim myArgs as sql::Arguments
                if *count(e.dirtyColumns.R1) > 1 then
                for each choice in e.dirtyColumns.R1
                tracker = tracker + 1
                if len(myfilter)>0 then
                myfilter = myfilter + " and " +choice.value+" = "
                myfilter = myfilter+":fld"+remspecial(str(tracker))
                myfilter = "where " + choice.value + " = :fld1"
                end if
                myfilter = "where " + e.dirtyColumns.R1 + " = :fld1"
                end if
                Attached Files
       is a great site to test and share sql code


                • #9
                  Thank you!! Sorry did not realize you answered this also. THANK YOU


                  • #10
                    I can't be the only one that gets wrapped up in work stuff and doesn't have time to check the message board.
                    Did it work for you?
           is a great site to test and share sql code


                    • #11
                      yes, thank you! I used a combination of yours and Al's! I have been able to use these routines in multiple places - making life so much easier lol Thank you!


                      • #12
                        Gary's answer is absolutely correct.

                        I do want to point out that it is not always possible to hard-code the date(s) for a SQL expression, and if you need to use a date variable, Alpha provides the ability to turn that into a SQL correct date with the function: format_data() - note that the function is format_DATA, not format_DATE
                        From the interactive window.
                        a = {01/01/2021}

                        = {01/01/2020}

                        = "2020-01-01"
                        There are other ways to bring dates into SQL format, but this is a very concise way to do it.

                        Hope this helps.
                        Jay Talbott
                        Lexington, KY


                        • #13
                          Ok, thank you! We do convert dates to SQL format but I think using a different method - so this is good to know! Thanks!