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 executing SQL Count query: when using a UX to edit a list control item.

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

    Error executing SQL Count query: when using a UX to edit a list control item.

    ISSUE: Receiving "Error executing SQL Count query": when using a UX to edit a list control item.

    When clicking the list item and invoking the Active Javascript to "EditExistingItem"
    • DB is MySQL
    • Using primarykey as the return value.
    • Using a GUID as a key.
    • In the list SQL statement, I disable the "Execute count query when query in preview? But it's reenabled the when I edit the statement!
    • The error displays in red at the top of the editor UX.


    Error executing SQL Count query:
    SELECT FIRST 1 commitments.commitment_id AS PRIMARYKEY_commitments_1, commitments.commitment_id AS commitments_commitment_id, commitments.description AS commitments_description, commitments.budget_id AS commitments_budget_id, commitments.vendor_ID AS commitments_vendor_ID, commitments.date_routed AS commitments_date_routed, commitments.ball_in_court AS commitments_ball_in_court, commitments.date_fully_exec AS commitments_date_fully_exec, commitments.commitment_type AS commitments_commitment_type, commitments.notes AS commitments_notes FROM commitments WHERE commitments.commitment_id = :PrimaryKey_1

    primarykey_1
    01572cfd-97d8-4d6b-860e-6b61cd1f39ae
    0
    Input
    Last edited by westridge; 09-24-2015, 04:53 PM.

    #2
    Re: Error executing SQL Count query: when using a UX to edit a list control item.

    I can add new columns, one at a time, to the underlying table. Next I can update the List control UX to show the new field. Then I can add the one more field to the detail/input UX. and all is well. When I try to add more than one column I get the SQL count query.
    Last edited by westridge; 09-25-2015, 08:12 PM.

    Comment


      #3
      Re: Error executing SQL Count query: when using a UX to edit a list control item.

      SOLUTION:

      Through the process of elimination and healthy dose of persistence, the root cause was found. A date column was named "date_fully_exec." in a MySQL table.
      Only after renaming the column to "dateexecutedfully" and rebinding the components to the renamed column was the error eliminated.

      Lesson Learned: DO NOT use the phrase/word "exec" as a part of your field names. With all that dynamic code running in Alpha, I suspect the parser got confused.

      WOW, there are several hours of my life that I want back.

      Comment


        #4
        Re: Error executing SQL Count query: when using a UX to edit a list control item.

        Nice sleuthing... thanks for posting the results of your persistence. Never would have guessed that one. I understand what you mean, but... those exhausting hours are really valuable.

        Comment


          #5
          Re: Error executing SQL Count query: when using a UX to edit a list control item.

          Originally posted by Davidk View Post
          Nice sleuthing... thanks for posting the results of your persistence. Never would have guessed that one. I understand what you mean, but... those exhausting hours are really valuable.
          Thank you for taking a look David.

          Comment


            #6
            Re: Error executing SQL Count query: when using a UX to edit a list control item.

            Version used when issue encountered: Alpha Anywhere v.3.5 Build 2999 / add-in build 4915

            Comment

            Working...
            X