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

Update indexes before form loads

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

    Update indexes before form loads

    Is there a way to update all indexes for a set just prior to a form for that set loading?
    Thank you,
    Mike Konoff

    #2
    RE: Update indexes before form loads

    Mike,

    This should update the indexes of the primary table, which is how the set indexes are determined, I think.

    "tbl".update_production_index()
    Syntax:
    "Tbl".update_production_index()
    Description:
    Updates all of the indexes in the production index of the table referenced by
    "Tbl".
    The production index is the index file with the same name as the table. The
    production index is opened automatically when the table is opened.
    Example:
    'This script updates the indexs for the current table.
    '------------------------------------------------------------------
    tbl = table.current()
    idx = tbl.update_production_index()
    See Also:
    "tbl".index_tag_add(), Table.index_create_begin(), Table.index_add(),
    "tbl".index_create_end(), "index".update()
    There can be only one.

    Comment


      #3
      RE: Update indexes before form loads

      Stan,
      Is it necessary or advisable to open the tables in exclusive mode before updating the production index?

      -- tom

      Comment


        #4
        RE: Update indexes before form loads

        Tom,

        Appreciate the suggestion. My first reply was really only dealing with the question of the method to update the indexes. (I'm sure you recognize it as cut-and-paste from the online documentation)

        I would suggest exactly what you said, as well as error trapping to alert the user if the table(s) could not be opened in exclusive mode. As I understand it, if exclusive mode is not available and you don't check for that condition, the index update will not occur, but no error is returned.

        Thanks,

        Stan
        There can be only one.

        Comment


          #5
          RE: Update indexes before form loads

          Yes, I recall bumping into this myself I believe. It was hard to spot because in a script which updated the indexes for several tables they all looked like they had run to completion, when in fact, only those which were successfully opened in exclusive mode actually got reindexed. I've since changed my error trapping to do a better job of calling these situations to my attention.

          Thanks for your assistance.

          -- tom

          Comment


            #6
            RE: Update indexes before form loads

            Thanks for the advice guys.

            I was able to do what I wanted by using .update_production_index().

            Took me a while to figure out, but I got it to work. I've never really used xbasic, so it's a whole new ballgame for me.

            I see that there I have a number of indexes while there is only one .cdx file. In A4 there was a seperate file for each index file. Are all indexes within the .cdx file in A5?

            Thanks again,
            Mike
            Thank you,
            Mike Konoff

            Comment


              #7
              RE: Update indexes before form loads

              Mike - yes, all indexes are in the .cdx file.

              About your original question - even though you CAN do what you ask, is it really a good idea ?

              If you are in a multi-user environment, if another user has a form open for the same .dbf or set, you couldn't get access to the file, and if you were indexing, they, in turn,
              couldn't get access.

              Secondly, even if you are the only one on, or a single user system, it would seriously degrade performance to wait for a re-index every time you opened a form, unless you have pretty small files with few indexes.

              Thirdly, I have always felt that is totaly unnecessary to
              rebuild the indexes unless you have a reason to suspect that
              there is a problem - for example, a power outage, or just getting wierd results. Indexes can get corrupted, and you should probably have a method to do them all at once, and
              do a weekly or monthly maintenance run.

              Just a thought.

              Lowell :-)

              Comment


                #8
                RE: Update indexes before form loads

                Unless you create a named index for some other purpose, yes.
                There can be only one.

                Comment

                Working...
                X