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

Query limit at 255?

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

    Query limit at 255?

    Hi

    I am trying to weed out duplicate customers in a table with thousands of records.
    So I read the first phone number and query the table for duplicates,
    then the next record, query again...

    Strangely enough, regardless at what record I start, after 255 queries the program throws an exception.

    Below is the dumbed down code, where I query the same phone number over and over. It will give 3 duplicates found 254 times and then Boom! Where can I see what the exception is? ( it only say "an error occurred" )


    FOR i = 1 TO 1000 STEP 1

    vPhone="2175325555"
    query.filter="Phone= " + s_quote(vphone)
    query.options = ""
    query.order = "recno()"

    qry = tbl.query_create()
    nrecs = qry.records_get()

    qry.drop()
    nrecs =0
    NEXT

    #2
    Re: Query limit at 255?

    Eriks

    2 ideas to work with.
    Backup backup backup

    1. Run a summary operation, group on telephone number and use the count for each telephone number.

    2. Use the delete duplicate utility option. Control panel - right the table - utilities - delete duplicates - there is a subsystem to help you. Works great.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      Re: Query limit at 255?

      You could also try

      Code:
      FOR i = 1 TO 1000 STEP 1
      
      vPhone="2175325555"
      query.filter="Phone= " + s_quote(vphone) 
      query.options = ""
      query.order = "recno()"
      
      qry = tbl.query_create()
      nrecs = qry.records_get()
      tbl.query_detach()
      [COLOR="Blue"]'or
      'tbl.QUERY_DETACH_ALL()[/COLOR]
      nrecs =0 
      NEXT
      There can be only one.

      Comment


        #4
        Re: Query limit at 255?

        Stan's suggestion worked for me recently, had a complex nested loop that needed to conditionally update about 30k records and
        Code:
        tbl.QUERY_DETACH_ALL()
        worked a treat. Also a great cure for insomnia! Just opened up windows explorer to the data folder and watched the .mpx files open and close... open and close ... open and close! :-)
        Glen Schild



        My Blog

        Comment


          #5
          Re: Query limit at 255?

          Thanks guys, BUT

          unfortunately it will not work (yet) for me:

          The tbl.query_detach() did not do anything and the tbl.query_detach_All() throws a different error:

          The precess cannot access the file because it's used by another process

          c:\..\local settings\temp\$$091818.mpx

          I steps through the program, and both variations actually perform the command, the "All" fails at the first try.


          ( Al, I can't use your suggestions - I need to merge the records, not just delete them).

          Comment


            #6
            Re: Query limit at 255?

            In similar instances I've found it much faster to step through a sorted table. Here if the table were sorted by phone number all the numbers that would be returned by a query are already grouped together, right? Do your processing in tight loops stepping through all the records that have the same phone number. When the next fetch returns a different phone number, start over. Not one query is needed.

            Comment


              #7
              Re: Query limit at 255?

              The precess cannot access the file because it's used by another process
              c:\..\local settings\temp\$$091818.mpx
              This error will be thrown if the tbl.query_detach_all() is encountered before the intervening code has finished executing. Can happen if you have some sort of operation converted to xbasic which hasn't completed. for example.

              What steps are you taking to "Merge" the duplicates inside your loop.
              There can be only one.

              Comment


                #8
                Re: Query limit at 255?

                Tom and Stan,

                Tom, thanks for the tip, I will try this - especially if you think it's faster.
                Stan, I am not even at the point to merge anything, since the loop finding it stalls.
                Also I can put a debug(1) in front of the detach_all and wait 20 sec - and it will still fail.

                Comment


                  #9
                  Re: Query limit at 255?

                  Eriks

                  Have you tried option 2 of post 2?

                  I think you really need to consider it.
                  Al Buchholz
                  Bookwood Systems, LTD
                  Weekly QReportBuilder Webinars Thursday 1 pm CST

                  Occam's Razor - KISS
                  Normalize till it hurts - De-normalize till it works.
                  Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                  When we triage a problem it is much easier to read sample systems than to read a mind.
                  "Make it as simple as possible, but not simpler."
                  Albert Einstein

                  http://www.iadn.com/images/media/iadn_member.png

                  Comment

                  Working...
                  X