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

SQL Expression I am stumped on this one

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

    SQL Expression I am stumped on this one

    I have a report that uses the Alpha SQL statement builder (instead of a view) and am stuck on a parse error on one of the expressions

    These expressions work .....
    if( status = 'Active' , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) )
    if( CurrentDate() < :r_from , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) )
    if( CurrentDate() < start_date , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) )

    I did this to prove to myself all dates are legit dates in the correct format. What I really need to do is .....

    if( start_date >= :r_from , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) )

    but when I use start_date and the argument :r_from together in the first operand of the IF statement, I get a Alpha parsing error message

    Any suggestions would be very helpful. I try to do most data handling in SQL views but in this case I need to use arguments in the SQL statement as part of an expression. Is there any way of switching to a SQL view and use the arguments defined in Alpha ?

    #2
    Re: SQL Expression I am stumped on this one

    I haven't tried your expression (I would if you had supplied an example without args) but wonder if you might try it without PortableSQL enabled?
    -Steve
    sigpic

    Comment


      #3
      Re: SQL Expression I am stumped on this one

      Hi Steve, tried changing from Portable to Native but Alpha spit out a handful of errors

      Here's one statement that works
      SELECT Company_ID, EmpID, (( rtrim(lastname) + ', ') + rtrim(firstname) ) AS empname, start_date, end_date, [pay type], fulltime_parttime, [FTE Hours], status, if( CurrentDate() <= :r_from , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) ) AS weeks1
      FROM employee_master

      but if I change CurrentDate() to the field "start_date", I get a parsing error. Interestingly enough, if I keep CurrentDate() and change the :r_from arg to be the "start_date" field, there is no error. I only get the parsing error when I try to use start_date and the :r_from arguments together in the IF statement. Either operand will work when used with CurrentDate() or a hardcoded date value, but not together. I am befuddled.....

      I know you asked for the statement without the args, but that won't help me figure this out. The parsing error comes when using an argument and a field together in the IF compare. I've already tried lots of combinations and can get either to work against anything other than each other

      Comment


        #4
        Re: SQL Expression I am stumped on this one

        You can use arguments in the where clause of a view query just like you would a table. Or you can build the query yourself in the onSQLSelectQuery event. Or you can create a stored procedure and pass arguments. Note that the latter two get complicated if you want to use a search part on top of that.

        Comment


          #5
          Re: SQL Expression I am stumped on this one

          This is a report so there's no event trigger that I know of (onSQLSelectQuery)
          I got tired of struggling with this so I went the cheesy route... created 3 seperate SQL expressions to calculate the different possible # of weeks elapsed fields. Then in the report, I created a column with an expression that tests for additional conditions I set in the SQL expression in the false result to determine which of the 3 possibilites to print. I know some day I'll go back to this report and wonder why in the world I did it this way... but that'll be a new day

          As always, thanks for the input

          Comment


            #6
            Re: SQL Expression I am stumped on this one

            Originally posted by ids-dave View Post
            Hi Steve, tried changing from Portable to Native but Alpha spit out a handful of errors

            Here's one statement that works
            SELECT Company_ID, EmpID, (( rtrim(lastname) + ', ') + rtrim(firstname) ) AS empname, start_date, end_date, [pay type], fulltime_parttime, [FTE Hours], status, if( CurrentDate() <= :r_from , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) ) AS weeks1
            FROM employee_master

            but if I change CurrentDate() to the field "start_date", I get a parsing error. Interestingly enough, if I keep CurrentDate() and change the :r_from arg to be the "start_date" field, there is no error. I only get the parsing error when I try to use start_date and the :r_from arguments together in the IF statement. Either operand will work when used with CurrentDate() or a hardcoded date value, but not together. I am befuddled.....

            I know you asked for the statement without the args, but that won't help me figure this out. The parsing error comes when using an argument and a field together in the IF compare. I've already tried lots of combinations and can get either to work against anything other than each other
            :r_from is being treated as/set as a date, yes? And start_date is a date type as well? It seems maybe the system might not understand that start_date and :r_from are both date types in that scenario.

            Curious: if your change your expression from start_date >= :r_from to DaysBetweenDates(start_date, :r_from) <= 0, does that get you what you want? If start_date is greater than :r_from, then the DaysBetweenDates function is going to return a negative value. If they're equal, it returns 0.

            Maybe yes?
            Alpha Anywhere latest pre-release

            Comment


              #7
              Re: SQL Expression I am stumped on this one

              Hi Sarah, yes the date fields are valid date data types and each works when compared to a hardcoded date. The problem is Alpha is spitting out a SQL parsing error message even though the statement is valid.

              Your DaysBetweenDates suggestion was interesting so I just tried it and it works - no Alpha sql parsing error !

              No parsing error when the expression is coded as --> if( DaysBetweenDates(start_date, :r_from) <= 0 , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) ) AS weeks1

              but this expression gets a parsing error --> if( start_date <= :r_from , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) ) AS weeks1

              Both are valid SQL expressions but is another case of the Alpha parsing process kicking out an error when nothing is wrong

              Comment


                #8
                Re: SQL Expression I am stumped on this one

                Originally posted by ids-dave View Post
                Hi Sarah, yes the date fields are valid date data types and each works when compared to a hardcoded date. The problem is Alpha is spitting out a SQL parsing error message even though the statement is valid.

                Your DaysBetweenDates suggestion was interesting so I just tried it and it works - no Alpha sql parsing error !

                No parsing error when the expression is coded as --> if( DaysBetweenDates(start_date, :r_from) <= 0 , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) ) AS weeks1

                but this expression gets a parsing error --> if( start_date <= :r_from , DATEDIFF(week, :r_from, :r_to) , DATEDIFF(week, :r_from, end_date) ) AS weeks1

                Both are valid SQL expressions but is another case of the Alpha parsing process kicking out an error when nothing is wrong
                I would recommend sending your wee expression into Alpha to see if that isn't some sort of bug maybe? Or maybe the argument isn't being set properly or is converting to a string for bizarre reasons? Or maybe your start_date was being converted to a string? It doesn't make sense to me that the date function would work but date comparison would fail for a date field in your DB and a date argument. So strange.
                Alpha Anywhere latest pre-release

                Comment

                Working...
                X