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 Index within script

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

    Update Index within script

    I have a script which requires that I update an individual index after a variable has been set.

    This works:

    idx = inputf.update_production_index()

    but is there a more efficient way so that just one index is updated and not all indexes.

    Thanks

    Tom

    #2
    RE: Update Index within script

    Tom,

    I'm curious why you're using variables with production indexes. Folks often recommend that variables NOT be used in index filters. Off hand I can't imagine any other uses. How are you using variables with your index?

    -- tom

    Comment


      #3
      RE: Update Index within script

      Hi Tom,

      I have a button on a form that eventually does an update on charges. But first and variable set from an array to identify the PAYOR, then the SERVICES for this Payor are shown in the next array for selection. This permits CHARGES to be updated for Specific PAYORS for specific SERVICES.

      So after the variable for the payor is set, vPayor, then I have a filter in SERVICES.dbf to filter on vPayor to show services paid by this payor.

      Guess I could use a query, but I am more familiar with indexes. ANyway, the filtered index in SERVICES needs to be refreshed or updated between the PAYOR array and SERVICES array.

      I'm open to suggestions and alternative approaches.

      Tom

      Comment


        #4
        RE: Update Index within script

        Tom,

        Is the filter in your index for SERVICES using the variable somehow?

        -- tom

        Comment


          #5
          RE: Update Index within script

          Yes - it sure is.

          But apparently when you use the index_primary_put() method it does not Update the index. And the index needs updating to see the just set variable filter.

          Is there a more efficient way to update the index just prior to using it?

          Tom

          Comment


            #6
            RE: Update Index within script

            Tom,

            I have no experience doing what you are describing. Others (with more experience than I) have indicated that this is dangerous and problematic. In the best case you will have to rebuild the index every time the value of the variable changes, in the worst case the variable value will change and you'll miss the rebuild, causing the index to become corrupted.

            If it were me I'd look at other alternatives.

            Tell us what you're shooting for, and perhaps we can suggest some.

            -- tom

            Comment


              #7
              RE: Update Index within script

              Hi Again,

              Like I say this will work:

              idx = inputf.update_production_index()

              And I don't mind having to rebuild the indexes each time I use it, because the variable is set within the same script. BUT I think the above code updates all the indexes and I'd prefer to just update the one index I'm using.

              Apparently, the indx.get() and Put() methods do not rebuild the indexes.

              Thanks again,

              Tom

              Comment


                #8
                RE: Update Index within script


                Tom, I checked the Xbasic Ref. Manual and the discussion does not extend to updating only a single indextag. You may be thinking of Alpha Four, where indexes were maintained in separate files, each ending in an NDX extension. Updating (rebuilding) a single index was possible there. As you know Alpha Five keeps all the indexes for a single table in a compound index file, which is a single file bearing a CDX extension. I don't know of a way to update just one indextag.

                -- tom

                Comment


                  #9
                  RE: Update Index within script

                  Thanks for looking into this Tom.

                  Like I say, I have it working - but..

                  Again, Thanks

                  Tom

                  Comment

                  Working...
                  X