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

QBE Error

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

    QBE Error

    Hoping someone can point me in the right direction.

    I set up QBE on a grid, and when I click on the filter icon, and choose QBE Syntax, I get the following error:

    Error running Grid:
    Could not get count of records in query.
    Database API specific error

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

    -3100 - '[Microsoft][ODBC Microsoft Access Driver] Syntax error (missing operator) in query expression '(VendNum = Pa_RaM000) AND (( ()))'.
    SQL State is: 42000'
    TIP: To see the SQL statement that caused the error, edit the Grid component, go to Properties, Advanced, Other
    Enter this command 'tmpl.showErrorDetail = .t.', then re-run the Grid

    I am a newbie, and have to admit that I don't even know what choosing "QBE SYntax" from the menu was supposed to do. I was guessing that it would bring up some help explaining the query syntax to the user.

    Why is this error occurring?

    Also, how do you gracefully handle such errors? I have gotten similar errors before while experimenting with grids, and I haven't figured out how to recover other than closing the browser window and relaunching the preview.

    Thanks.

    #2
    Re: QBE Error

    Good question, I use QBE in a bunch of grids but never selected "QBE Syntax" & I don't know what it is supposed to do. I quickly tested with a DBF based grid: the error does not occur. With a SQL based grid using the Northwind database is does occur so it smells like a bug. I'll report it.
    Frank

    Tell me and I'll forget; show me and I may remember; involve me and I'll understand

    Comment


      #3
      Re: QBE Error

      You are correct; I just tried a dbf table, and did not get the error, but, it is still a total mystery what the "QBE syntax" menu selection does. Even without the error, it doesn't seem to do anything. I checked the help documentation, and, although it does have a screen shot showing the menu, it makes no mention about what that particular option does.

      Comment


        #4
        Re: QBE Error

        Chris,

        QBE for example allows to search for 2 criteria in the same field; if you yahev a table customers containing a field "city" then qbe would allow to enter "london,paris" in the qbe textbox, then click the icon & select qbe syntax and all customers in london & paris will be shown. I'm still thinking of an article or video outlining the complete qbe syntax but I can't seem to find that right now.
        Frank

        Tell me and I'll forget; show me and I may remember; involve me and I'll understand

        Comment


          #5
          Re: QBE Error

          Reading the v12 releasenotes it seems that apart from using a comma you can also use && as an operator to combine criteria. See http://downloads.alphasoftware.com/a...easenotes.html and search for "qbe"
          Frank

          Tell me and I'll forget; show me and I may remember; involve me and I'll understand

          Comment


            #6
            Re: QBE Error

            Here's the original documentation on Query By Example syntax - doesn't help your error, just a reference.
            http://wiki.alphasoftware.com/Search...rch+Syntax+V10


            Edit: Sorry, just realised this is documentation for the Query by Form in the search part of a grid; however, the expressions are still valid in the QBE headings in the grid- I use this functionality in several applications
            Last edited by marvinbase; 02-03-2015, 11:11 AM. Reason: clarification

            Comment


              #7
              Re: QBE Error

              yep that's it!
              Frank

              Tell me and I'll forget; show me and I may remember; involve me and I'll understand

              Comment


                #8
                Re: QBE Error

                Yes, Frank, you are correct. The "QBE Syntax" menu item does exactly what you said. I did not know that a QBE form would not accept the syntax by default, but it makes sense.
                What threw me is that you can use Query By Form syntax by default in a grid search part. I have not compared the syntax of QBF vs QBE to see what the difference is yet.

                This has given me the idea to build a help window into my app that explains the QBE syntax to the user.

                In any event, I have verified on another machine that you get the QBE error on SQL tables, but not on Access tables.

                I may have discovered some other peculiar behavior, but need to do some more testing.

                Comment


                  #9
                  Re: QBE Error

                  Chris,

                  It was a confirmed bug and it has been fixed today so the next pre-release will contain it.
                  Frank

                  Tell me and I'll forget; show me and I may remember; involve me and I'll understand

                  Comment

                  Working...
                  X