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 message: Maximum number of indexes exceeded?

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

    Error message: Maximum number of indexes exceeded?

    I have a form based on a table. The user enters data into fields on the form, and then clicks the save button. This works fine. However, when entering many records one after the other, I get this error message: "Max number of indexes exceeded", and I have no way out other than to exit the program and restart it. Doe s anyone know what causes this and how to avoid this error?

    Gary
    Gary S. Traub, Ph.D.


    #2
    RE: Error message: Maximum number of indexes excee

    Never got that one, and we've had a ton of indexes.

    Does your data entry process, or records search, or some form of user interaction, generate a lot of queries which might not be getting erased?

    Comment


      #3
      RE: Error message: Maximum number of indexes excee

      Hi Jim:

      Thanks for your prompt response. I believe that the answer to your question is no. I do not think I am generating a lot of indexes. But maybe I am missing something. This is the script that is attached to a save button:

      dim ttest as n
      ttest=0
      dim tempidn as c
      tempidn=idnumber.value
      dim global anum as n
      dim global fname as c
      fname=fullname_new.value

      if time_new.value=""
      ui_msg_box("You must indicate the time of the appointment","")
      time_new.activate()
      ttest=1
      end if
      if fullname.value="" .and. ttest=0
      ui_msg_box("You cannot leave the Patient field blank","")
      fullname_new.activate()
      ttest=1
      end if
      if svcode_new.value="" .and. ttest=0
      ui_msg_box("You cannot leave the SVCODE field blank","")
      svcode_new.activate()
      ttest=1
      end if

      if ttest=0

      dim tblt as p
      tblt=table.open("authorizations")
      query.filter="idnumber=tempidn"
      query.order=""
      query.options=""
      tblt.query_create()
      dim tn as n
      tn=0
      while .not. tblt.fetch_eof()
      tn=tn+1
      tblt.fetch_next()
      end while
      tblt.close()
      if tn>0

      dim ch as n
      dim deltit as c
      dim code as n
      code=UI_YES_NO
      deltit="Apply to an authorization?"
      ch=ui_msg_box(deltit,"",code)
      if ch=ui_no_selected then
      anum=0
      else if ch=ui_yes_selected then

      script_play("ChangeAuthBtn")
      'dim global anum as n
      tempauthno_new.value=anum
      if tempauthno_new.value=0
      svcode_new.activate()
      anum=0
      end
      end if
      end if
      end if

      ui_freeze(.t.)

      dim ttime as c
      dim tname as c
      dim tsvcode as c
      dim tfee as n
      dim tunits as n
      dim ti1exp as n
      dim ti2exp as n
      dim tptexp as n
      dim tprovfee as n
      dim tt as c
      dim tl as c
      dim tdxcode as c
      dim tmod as c
      dim tnotes as c
      dim tdate as d
      dim tprov as c
      dim tempidn as c
      dim global showdate as d
      dim global showprov as c
      ttime=time_new.value
      tname=fullname_new.value
      tsvcode=svcode_new.value
      tfee=fee_new.value
      tunits=units_new.value
      ti1exp=i1exp_new.value
      ti2exp=i2exp_new.value
      tptexp=ptexp_new.value
      tprovfee=provfee_new.value
      tt=t_new.value
      tl=l_new.value
      tdxcode=dxcode_new.value
      tmod=mod_new.value
      tnotes=notes_new.value
      tdate=showdate
      tprov=showprov
      tempidn=idnumber_new.value

      parent.cancel()
      parent.commit()

      dim tbl as p
      tbl=table.get("appointments")
      tbl.enter_begin()
      tbl.authno=anum
      tbl.tempauthno=anum
      tbl.time=ttime
      tbl.fullname=tname
      tbl.svcode=tsvcode
      tbl.fee=tfee
      tbl.units=tunits
      tbl.i1exp=ti1exp
      tbl.i2exp=ti2exp
      tbl.ptexp=tptexp
      tbl.provfee=tprovfee
      tbl.t=tt
      tbl.l=tl
      tbl.dxcode=tdxcode
      tbl.mod=tmod
      tbl.notes=tnotes
      tbl.date=tdate
      tbl.prov=tprov
      tbl.idnumber=tempidn
      tbl.appt="Y"
      tbl.charge="N"
      tbl.enter_end()
      dim cnum as n
      cnum=tbl.chargeno

      dim tblp as p
      tblp=table.open("patients")
      query.filter="idnumber=tempidn"
      query.order=""
      query.options=""
      tblp.query_create()
      tblp.change_begin()
      tblp.status="Active"
      tblp.change_end()
      topparent.resynch()
      tblp.close()

      query.filter="date=tdate .and. prov=tprov .and. appt='Y'"
      query.order="STR(TIMESORT,8,0)+SVCODE+FULLNAME"
      query.options=""
      tbl.query_create()

      browse1.enable()
      browse1.refresh()
      browse1.fetch_first()

      dim shared tempanum as n
      tempanum=tempauthno_new.value

      if tn>0
      if ch=ui_yes_selected
      script_play("AuthCountDownEdit")
      end if
      end if

      script_play("ApptBtnsShow")

      condtest=3
      cond1.refresh()

      ui_freeze(.f.)

      while cnumbrowse1:chargeno.value
      browse1.fetch_next()
      end while

      anum=0
      fname=""

      browse1.activate()

      end if

      end
      Gary S. Traub, Ph.D.

      Comment


        #4
        RE: Error message: Maximum number of indexes excee

        Gary, I'm not sure if this is the cause of your problem, but I find it odd that your validation routines at the top of your script do not stop the script when you return to the data entry form. It seems to me that your script keeps running, after you activate the field that is missing required data. What happens next, when the user presses the save button again after supplying the missing data? You might have two copies of the script running simultaneously. Wouldn't it be better to *end* the script if required fields are empty?

        -- tom

        Comment


          #5
          RE: Error message: Maximum number of indexes excee

          Tom:

          I will try what you are saying.But I believe that the script as is does end when the required field is not filled. Notice that when the "field rule" is violated it sets ttest to 1 and that the remiander of the script only runs if ttest=0. I believe that this is equivalent to what you are saying. But I may be wrong and will definitely try your suggestion. Thanks!

          Gary
          Gary S. Traub, Ph.D.

          Comment


            #6
            RE: Error message: Maximum number of indexes excee

            Perhaps so, it's virtually impossible to trace on line, since everything is left justified.

            -- tom

            Comment


              #7
              RE: Error message: Maximum number of indexes excee

              Gary, you might want to review the external scripts which get 'played' by this one, to see if other queries are being run there which remain active.

              Also, you might want to freeze the interface until the script runs its course. Depending on the sizes of these tables, and the speed of your network, your operator may be saving the next record before the current one is finished.

              For example, the statements in your script which refresh or resynch the current form could be delayed to the end of the script. Or, even better, the save button could be disabled until the script concludes...

              -- tom

              Comment


                #8
                RE: Error message: Maximum number of indexes excee

                Tom:

                These are all good suggestions, and I will try them. Thanks.

                Gary
                Gary S. Traub, Ph.D.

                Comment


                  #9
                  RE: Error message: Maximum number of indexes excee

                  Gary:

                  I've had that (or a similar error) in scripts which run queries repetitively. Unless, that is, you drop the query when yuo are done with it since Alpha will only store X # of active queries. Perhaps Alpha is counting the queries as you continue with data entry in a given session.

                  I'd try changing the query action line to

                  idx=tbl.query_create()

                  and add an

                  idx.drop()

                  when you no longer need the query. The idx.drop must come before the tbl.close() line.

                  Finian
                  Finian

                  Comment


                    #10
                    RE: Error message: Maximum number of indexes excee

                    Finian:

                    Once again, thanks! This is absolutely the source of my problem.

                    Have a great day ...

                    Gary
                    Gary S. Traub, Ph.D.

                    Comment

                    Working...
                    X