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 error message: expecting RPAREN, found "LEFT"

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

  • SQL error message: expecting RPAREN, found "LEFT"

    I am trying to create a grid against a remote Database accessed via AlphaDAO. I want to base it on a SQL Select Statement, but when I insert the SQL statement it gives me the following error: line 82:1: expecting RPAREN, found “LEFT”. I am not sure why it is giving me this error because my whole database was created with no problems using the same statement. Has anybody ever encountered this error message?

  • #2
    Re: SQL error message: expecting RPAREN, found "LEFT"

    I think if you look at your sql select syntax you will find an error. That's what it was for me.
    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

    Comment


    • #3
      Re: SQL error message: expecting RPAREN, found "LEFT"

      I Second that
      Cheers
      Mauricio

      Comment


      • #4
        Re: SQL error message: expecting RPAREN, found "LEFT"

        What is your SQL query?

        Comment


        • #5
          Re: SQL error message: expecting RPAREN, found "LEFT"

          Sorry for the slow reply. Here is my SQL statement:

          SELECT
          PostFile.TrNum,
          PostFile.Dte AS DOS,
          PostFile.TDate AS DOE,
          PostFile.PtNum AS PatientNumber,
          IdentFil.ChartNum,

          ALLTRIM(IdentFil.LastNam) AS PatientLastName,
          ALLTRIM(IdentFil.FirstNam) AS PatientFirstName,
          IIF(ISNULL(IdentFil.MidInit), ' ', IdentFil.MidInit) AS PatientMI,
          IdentFil.Title1 AS PatientTitle,

          ALLTRIM(
          ALLTRIM(IdentFil.LastNam) + ', ' +
          ALLTRIM(ALLTRIM(IdentFil.FirstNam) + ' ' +
          IIF(ISNULL(IdentFil.MidInit), ' ', IdentFil.MidInit))) AS PatientFullName,

          IdentFil.Address1 AS PatientAddress1,
          IdentFil.Address2 AS PatientAddress2,
          IdentFil.City AS PatientCity,
          IdentFil.State AS PatientState,
          IdentFil.Zip AS PatientZip,
          IdentFil.LastPayDt AS PatientLastPayDate,
          IdentFil.LastPayAmt AS PatientLastPayAmt,

          SUBSTR(IdentFil.HomPhone, 1, 3) + "." +
          SUBSTR(IdentFil.HomPhone, 4, 3) + "." +
          SUBSTR(IdentFil.HomPhone, 7) AS PatientHomePhone,

          LEFT(IdentFil.BusPhone, 3) + "." +
          LEFT(RIGHT(IdentFil.BusPhone, 7), 3) + "." +
          RIGHT(IdentFil.BusPhone, 4) AS PatientWorkPhone,

          DocIdent.Doc AS DocCode,
          DocIdent.Name AS DocLastName,
          DocIdent.FirstName AS DocFirstName,
          DocIdent.MidInit AS DocMI,
          DocIdent.Title AS DocTitle,
          DocIdent.Creds AS DocCreds,
          DocIdent.Address1 AS DocAddress1,
          DocIdent.Address2 AS DocAddress2,
          DocIdent.City AS DocCity,
          DocIdent.State AS DocState,
          DocIdent.Zip AS DocZip,
          DocIdent.Group_Name AS DocGroupName,
          DocIdent.Phone AS DocPhone,
          DocIdent.FAX AS DocFax,

          ALLTRIM(
          IIF(ISNULL(DocIdent.Title), '', ALLTRIM(DocIdent.Title)) + ' ' +
          IIF(ISNULL(DocIdent.FirstName), '', ALLTRIM(DocIdent.FirstName)) + ' ' +
          IIF(ISNULL(DocIdent.MidInit), '', ALLTRIM(DocIdent.MidInit)) + ' ' +
          IIF(ISNULL(DocIdent.Name), '', ALLTRIM(DocIdent.Name)) +
          IIF(ISNULL(DocIdent.Creds), ' ',
          IIF(ALLTRIM(DocIdent.Creds) = '', '', ', ' + ALLTRIM(DocIdent.Creds)))
          ) AS DocFullName,

          Facility.Name AS HospitalName,

          I1.InsNum AS InsNum1,
          IIF(ISNULL(I1.CorpName), '', I1.CorpName) AS Carrier1,
          IIF(ISNULL(I1.Mnem), '', I1.Mnem) AS InsMnem1,

          SUM(IIF(P2.Explan = 'Ins.1', P1.Payment, 0.00)) AS Ins1Amount,
          SUM(IIF(P2.Explan <> 'Ins.1' AND SUBSTR(P2.Explan, 1, 3) = 'Ins', P1.Payment, 0.00)) AS Ins2Amount,
          SUM(IIF(P2.Explan = 'Patnt', P1.Payment, 0.00)) AS PatientAmount,
          SUM(IIF(P2.Explan = 'Other', P1.Payment, 0.00)) AS OtherAmount,
          SUM(IIF(P2.Typ = 'X', P1.Payment, 0.00)) As CreditAmount,

          PostFile.Explan,
          PostFile.Amount AS ChargeAmount,
          PostFile.Applied AS TotalPaid,
          PostFile.Ins1 AS Ins1Balance,
          PostFile.Ins2 AS Ins2Balance,
          PostFile.PtNt AS PatientBalance,
          PostFile.Other AS OtherBalance,
          PostFile.Amount - PostFile.Applied AS ClaimBalance,
          vTotals.tamt

          FROM (((PostFile
          LEFT OUTER JOIN PmtAndChrg AS P1 ON PostFile.TrNum = P1.ChrgNum)
          LEFT OUTER JOIN PostFile AS P2 ON P1.PmtNum = P2.TrNum)
          LEFT JOIN IdentFil ON PostFile.PtNum = IdentFil.PtNum)
          LEFT JOIN DocIdent ON PostFile.Doc = DocIdent.Doc AND DocIdent.Doc <> ''
          LEFT JOIN PatIns AS PI1 ON PostFile.PtNum = PI1.PtNum AND PI1.InsOrder = 1
          LEFT JOIN InsIdent AS I1 ON PI1.InsNum = I1.InsNum
          LEFT JOIN DocIdent AS Facility ON PostFile.Lab_Nbr = Facility.Hsp AND Facility.Typ = 'C'
          left join vtotals on vtotals.ptnum = postfile.ptnum

          WHERE
          PostFile.Typ = 'C'

          ORDER BY PostFile.PtNum, PostFile.Dte
          GROUP BY PostFile.TrNum

          Comment


          • #6
            Re: SQL error message: expecting RPAREN, found &quot;LEFT&quot;

            Originally posted by lfagerman View Post

            SUBSTR(IdentFil.HomPhone, 1, 3) + "." +
            SUBSTR(IdentFil.HomPhone, 4, 3) + "." +
            SUBSTR(IdentFil.HomPhone, 7) AS PatientHomePhone,

            LEFT(IdentFil.BusPhone, 3) + "." +
            LEFT(RIGHT(IdentFil.BusPhone, 7), 3) + "." +
            RIGHT(IdentFil.BusPhone, 4) AS PatientWorkPhone,
            Wow, what a select statement.

            I am not sure of why you are doing this in two different functions. I would think that the first method using substr() function would be the prefered way. It seems as though the error is pointing to the left() function. I would retry the statement without that section of code to pinpoint the error.
            Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

            Comment


            • #7
              Re: SQL error message: expecting RPAREN, found &quot;LEFT&quot;

              As far as I know alltrim is not an SQL function is an XBasic Function I think you are mixing things up the statemented should be in SQL language only
              http://www.made2mentor.com/2009/09/w...trim-function/
              Cheers
              Mauricio

              Comment


              • #8
                Re: SQL error message: expecting RPAREN, found &quot;LEFT&quot;

                Mauricio,

                alltrim() is one of Alpha's portable SQL functions. Here's a link to a list http://alphafivewiki.com/Portability+Functions Note the "Not Supported By" column in the link for database specifics.
                Jim Coltz
                Alpha Custom Database Solutions, LLC
                A5CustomSolutions.com
                jimcoltz@a5customsolutions.com

                Comment

                Working...
                X