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

Error parsing SQL statement Your database has returned the following error code and

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

    Error parsing SQL statement Your database has returned the following error code and

    Error parsing SQL statement

    Your database has returned the following error code and description to Alpha Five.
    Consult your database documentation for further information.

    91 - 'line 1:44: unexpected token: date_sub'

    UPDATE co_grouporders_list SET cutoff_date=date_sub(delivery_date, INTERVAL :noticeTimeMin MINUTE), approval_date=delivery_date-INTERVAL :approvalTimeMin MINUTE WHERE grpord_id=:grpOrdId AND fn_GetOrderCountForGroupOrderId(:grpOrdId)=0 AND (SELECT stop FROM co_grouporders WHERE id=:grpOrdId)=1;UPDATE co_grouporders_list SET cutoff_date=date_sub(delivery_date, INTERVAL :noticeTimeMin MINUTE), approval_date=NULL WHERE grpord_id=:grpOrdId AND fn_GetOrderCountForGroupOrderId(:grpOrdId)=0 AND (SELECT stop FROM co_grouporders WHERE id=:grpOrdId)=0;




    This is SO misleading.
    My database did NOT return this error - Alpha's parser did. This statement doesn't even hit the database - as Alpha decided it wasn't valid. Because apparently I can't use date_sub().
    Is there something I'm missing here?

    Calling a function in an insert is not allowed or something?
    Scott Moniz - Computer Programmer/Analyst
    REA Inc.
    http://reainc.net
    (416)-533-3777
    [email protected]

    REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
    If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
    contact us to discuss options.

    #2
    Re: Error parsing SQL statement Your database has returned the following error code

    UPDATE co_grouporders_list SET cutoff_date=date_sub(delivery_date, INTERVAL 20 MINUTE),
    approval_date=delivery_date-INTERVAL 20 MINUTE WHERE grpord_id=55 AND
    fn_GetOrderCountForGroupOrderId(55)=0 AND (SELECT stop FROM co_grouporders WHERE id=55)=1;
    UPDATE co_grouporders_list SET cutoff_date=date_sub(delivery_date, INTERVAL 20 MINUTE),
    approval_date=NULL WHERE grpord_id=55 AND fn_GetOrderCountForGroupOrderId(55)=0
    AND (SELECT stop FROM co_grouporders WHERE id=55)=0;

    COMPLETELY valid.
    MySQL Workbench doesn't complain.
    The Alpha parser does - this isn't the first time.
    So frustrating!
    Scott Moniz - Computer Programmer/Analyst
    REA Inc.
    http://reainc.net
    (416)-533-3777
    [email protected]

    REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
    If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
    contact us to discuss options.

    Comment


      #3
      Re: Error parsing SQL statement Your database has returned the following error code

      http://msgboard.alphasoftware.com/al...+sql+statement (UNSOLVED)
      Scott Moniz - Computer Programmer/Analyst
      REA Inc.
      http://reainc.net
      (416)-533-3777
      [email protected]

      REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
      If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
      contact us to discuss options.

      Comment


        #4
        Re: Error parsing SQL statement Your database has returned the following error code

        Once again:UPDATE co_grouporders_list SET cutoff_date=delivery_date-INTERVAL :noticeTimeMin MINUTE, approval_date=delivery_date-INTERVAL :approvalTimeMin MINUTE WHERE grpord_id=:grpOrdId AND fn_GetOrderCountForGroupOrderId(:grpOrdId)=0 AND (SELECT stop FROM co_grouporders WHERE id=:grpOrdId)=1;UPDATE co_grouporders_list SET cutoff_date=delivery_date-INTERVAL :noticeTimeMin MINUTE, approval_date=NULL WHERE grpord_id=:grpOrdId AND fn_GetOrderCountForGroupOrderId(:grpOrdId)=0 AND (SELECT stop FROM co_grouporders WHERE id=:grpOrdId)=0;

        Your database has returned the following error code and description to Alpha Five.
        Consult your database documentation for further information.

        81 - 'line 1:58: unexpected token: INTERVAL'
        Scott Moniz - Computer Programmer/Analyst
        REA Inc.
        http://reainc.net
        (416)-533-3777
        [email protected]

        REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
        If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
        contact us to discuss options.

        Comment


          #5
          Re: Error parsing SQL statement Your database has returned the following error code

          Looks like the Alpha parser didnt like 2 statements. Ok, thats fine - the error message didnt help at all in this case.

          But here comes yet ANOTHER problem - it just seems like its one after the other.

          dim sql as C
          sql="UPDATE co_grouporders_list SET cutoff_date=(delivery_date - INTERVAL 15 MINUTE), approval_date=(delivery_date - INTERVAL 15 MINUTE) WHERE grpord_id=55 AND fn_GetOrderCountForGroupOrderId(55)=0 AND (SELECT stop FROM co_grouporders WHERE id=55)=1"
          dim conn as SQL::Connection
          conn.Open("::name::conn")
          ?conn.execute(sql)
          = .F.

          ?conn.CallResult
          = API = ""
          Canceled = .F.
          Code = 100
          Error = .T.
          LastInsertedIdentity = <No data returned>
          NativeCode = 0
          NativeText = ""
          RowsAffected = 0
          Success = .F.
          Syntax = ""
          Text = "The database could not find the data you requested"
          Warnings = .F.


          conn.execute is returning false - which would lead most people to believe the statement failed. This is not the case - the statement runs but alpha "cleverly" tells me it didnt because no rows were updated...come on.

          Why not have conn.execute() return true - and let me check the rowsaffected variable. conn.execute()==.t. means execution was true, conn.execute()==.f. means execution did not go through.
          This is like having a didIDrinkCoffee() and returnin false cause i drank coffee but i also drank orange juice.

          conn.execute - i am interested in the execution failure/success - i dont care about rows affected in this case - because there may not be any - thats the whole point of a where clause. If theres no data to update - dont update it.

          //rant off

          sigh
          Scott Moniz - Computer Programmer/Analyst
          REA Inc.
          http://reainc.net
          (416)-533-3777
          [email protected]

          REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
          If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
          contact us to discuss options.

          Comment


            #6
            Re: Error parsing SQL statement Your database has returned the following error code

            Will checking for code 100 be reliable?
            Is code 100 used for anything else?

            I think i will just be checking the text property.

            IF conn.execute(sql)==.t. .OR. conn.CallResult.Text="The database cold not find the data you requested" then
            'call succeeded but alpha did not think so
            end if

            ridiculous workaround :/ oh well.

            you guys should really change conn.execute() so it reports only on execution. Just because an update had 0 rows affected does not mean it necessarily failed.
            Scott Moniz - Computer Programmer/Analyst
            REA Inc.
            http://reainc.net
            (416)-533-3777
            [email protected]

            REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
            If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
            contact us to discuss options.

            Comment


              #7
              Re: Error parsing SQL statement Your database has returned the following error code

              Default = FALSE (.F.). When this property is set to true, SQL statements passed to the ApplyData(), Execute(), ToOpenTable(), ToGridComponentDataObject(), ToOpenTable(), ToPropertyArray(), ToString(), ToXML(), and ValidateQuery() methods are checked to see if they are supported Portable SQL Statements and, if so, then translated to native syntax before being processed. Statements that are not supported are passed directly through to the underlying database driver as if PortableSQLEnabled were false.


              conn.PortableSQLEnabled=.f. did the trick.
              The documentation seems to be wrong - either portablesql is not the default - or something in my app set it to portable. "Statements that are not supported are passed directly through to the underlying database driver as if PortableSQLEnabled were false." - this doesnt seem to be true either - as statements that arent supported were being caught by alpha.
              Scott Moniz - Computer Programmer/Analyst
              REA Inc.
              http://reainc.net
              (416)-533-3777
              [email protected]

              REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
              If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
              contact us to discuss options.

              Comment


                #8
                Re: Error parsing SQL statement Your database has returned the following error code

                I am trying to use the same MySQL function in my code "DATE_SUB". I don't have to use this but it is what worked in MySQL for selecting data where Entrydate was within the past 30 day period. Is there another statement that I could use or could you tell me where you placed the conn.PortableSQLEnabled=.f. that corrected your problem.

                Code:
                SELECT Entrydate, L_NAME, f_name, m_name, address, cityLine, social_security, birth_date,  Sum(amount)  AS SumofAmount 
                FROM transactions 
                WHERE Entrydate >= DATE_SUB(CURDATE(),INTERVAL 30 DAY)
                GROUP BY social_security 
                ORDER BY L_NAME, f_name

                Comment


                  #9
                  Re: Error parsing SQL statement Your database has returned the following error code

                  Changed my code to:

                  Code:
                  SELECT Entrydate, L_NAME, f_name, m_name, address, cityLine, social_security, birth_date,  Sum(amount)  AS SumofAmount 
                  FROM transactions 
                  WHERE Entrydate >= ( CURDATE()  - 30) 
                  GROUP BY social_security 
                  ORDER BY L_NAME, f_name

                  Comment


                    #10
                    Re: Error parsing SQL statement Your database has returned the following error code

                    Originally posted by George Corder View Post
                    Changed my code to:

                    Code:
                    SELECT Entrydate, L_NAME, f_name, m_name, address, cityLine, social_security, birth_date,  Sum(amount)  AS SumofAmount 
                    FROM transactions 
                    WHERE Entrydate >= ( CURDATE()  - 30) 
                    GROUP BY social_security 
                    ORDER BY L_NAME, f_name
                    SOLUTION TO THIS:
                    found here

                    Comment

                    Working...
                    X