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

OVER_QUERY_LIMIT with google maps

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

    OVER_QUERY_LIMIT with google maps

    I get this message when I try to use the google maps feature with an alternate view. No matter how many record are displayed in the grid. Anyone know why?
    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/

    #2
    Re: OVER_QUERY_LIMIT with google maps

    You should only get that message if you are trying to show more tha 10 records at a time?

    Comment


      #3
      Re: OVER_QUERY_LIMIT with google maps

      Start referencing the long/lat rather than address as it is not limited.
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #4
        Re: OVER_QUERY_LIMIT with google maps

        Peter,
        That would be the perfect answer, but getting such data for UK postcodes is expensive to say the least!!

        Comment


          #5
          Re: OVER_QUERY_LIMIT with google maps

          Thanks everyone. Peter, your solution solved the problem.
          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


            #6
            Re: OVER_QUERY_LIMIT with google maps

            Originally posted by Kzin View Post
            Peter,
            That would be the perfect answer, but getting such data for UK postcodes is expensive to say the least!!
            Kzin you can not get public data over there with long/lat fields?
            I have every property in Suffolk, County New York which is public and has the long/lat data.

            If you can not get publicly then try making friends with guys the do GIS mapping cause there programs have it I betcha.
            Nicholas Wieland
            LedgerSuite.com Corp
            [email protected]
            http://www.ledgersuite.com

            Comment


              #7
              Re: OVER_QUERY_LIMIT with google maps

              There is a usage limit of 2.500 requests per day. See this document http://code.google.com/intl/nl-NL/ap...ion/geocoding/
              Frank

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

              Comment


                #8
                Re: OVER_QUERY_LIMIT with google maps

                Geocoding is the process of converting addresses (like "1600 Amphitheatre Parkway, Mountain View, CA") into geographic coordinates (like latitude 37.423021 and longitude -122.083739), which you can use to place markers or position the map. That is what you are allowed 2500 per day of if you have the lat/long there is not limit as I read the documentation.
                Nicholas Wieland
                LedgerSuite.com Corp
                [email protected]
                http://www.ledgersuite.com

                Comment


                  #9
                  Re: OVER_QUERY_LIMIT with google maps

                  I am getting the same over_query limit. My grid is set to only 10 records. Anything else I should check? The actual query is 137 records, but I am only displaying 10 at a time.

                  Comment


                    #10
                    Re: OVER_QUERY_LIMIT with google maps

                    Originally posted by lgrupido View Post
                    I am getting the same over_query limit. My grid is set to only 10 records. Anything else I should check? The actual query is 137 records, but I am only displaying 10 at a time.
                    Larry you answered your own question the query and what is returned is over 10 records it is 137 so it will fail it is not the grid page size it is because of 137 records returned and all bomb. You have to use Long/Lat and the problem goes away. Plus if you do not have the Long/Lat numbers Alpha was on the ball again as a function is provided to go out and get the Long/Lat if you have the address so of time you can get the proper data.
                    Nicholas Wieland
                    LedgerSuite.com Corp
                    [email protected]
                    http://www.ledgersuite.com

                    Comment


                      #11
                      Re: OVER_QUERY_LIMIT with google maps

                      Larry there is also a action script to getgeo info from google based on address.
                      Nicholas Wieland
                      LedgerSuite.com Corp
                      [email protected]
                      http://www.ledgersuite.com

                      Comment


                        #12
                        Re: OVER_QUERY_LIMIT with google maps

                        Actually, it IS the grid page size. When I move the grid size down to 5, it works.

                        It only sends addresses to the grid based on what is in the current grid. (At least that is what it says in the google maps A5 video.)

                        Unfortunately, I have hundreds of thousands of records in this database. At 2500 records a day - it will never get goecoded.

                        Comment


                          #13
                          Re: OVER_QUERY_LIMIT with google maps

                          You could write a function to use javascript to populate. Also there is a company that does the geocoding for you if you need it of course they charge for the service.
                          Nicholas Wieland
                          LedgerSuite.com Corp
                          [email protected]
                          http://www.ledgersuite.com

                          Comment


                            #14
                            Re: OVER_QUERY_LIMIT with google maps

                            FYI
                            Use of the Google Geocoding API is subject to a query limit of 2,500 geolocation requests per day. (User of Google Maps API for Business may perform up to 100,000 requests per day.) This limit is enforced to prevent abuse and/or repurposing of the Geocoding API, and this limit may be changed in the future without notice. Additionally, we enforce a request rate limit to prevent abuse of the service. If you exceed the 24-hour limit or otherwise abuse the service, the Geocoding API may stop working for you temporarily. If you continue to exceed this limit, your access to the Geocoding API may be blocked.

                            https://developers.google.com/maps/d...index?hl=nl-NL
                            Nicholas Wieland
                            LedgerSuite.com Corp
                            [email protected]
                            http://www.ledgersuite.com

                            Comment

                            Working...
                            X