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

"open index" error after tbl.range_add() V9

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

    "open index" error after tbl.range_add() V9

    I am migrating to a Version 9 Enterprise server and my 2 year old application is failing. I am getting an error suggesting an index is not open. This code has worked for the past 2 years on V7 and V8. Any ideas?
    Thanks,
    Ken


    It now reports the following error:

    a_tbl.range_add()
    Not an open index


    Here is the code sample:

    dim a_tbl as p
    dim indx as p
    dim tbegin as y
    dim errflag as c

    a_tbl = table.open("[PathAlias.ADB_Path]\Autosched.DBF")
    indx = a_tbl.index_primary_get()
    tbegin = ctot(time("0h:0m:s:2 AM",now()))
    range.flags = RANGE_INDEX .or. RANGE_FILTER .or. RANGE_MARKED
    range.index_pointer = indx
    range.filter = ""
    a_tbl.range_add()
    a_tbl.fetch_first()
    if a_tbl.is_marked()
    a_tbl.fetch_NEXT()
    end if
    a_tbl.fetch_first()
    a_tbl.range_drop()
    a_tbl.close()

    #2
    Re: "open index" error after tbl.range_add() V9

    Probably just reindex your tables.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: "open index" error after tbl.range_add() V9

      Thanks for the reply and of course that was the first thing that I tried. I am afraid I am missing something regarding my index file, xbasic or publishing that is messing things up.

      It works without error:
      1. In the interactive window (v9) on my system with the same files I ftp to the remote servers.
      2. In the thread on the V8 server (for the past 2 years)

      It fails:
      1. In the thread on the V9 server
      2. In an xbasic script placed on an .a5w page in either my V8 server OR v9 server! I have attempted this with other tables using the script and it never works. It always returns the error. I use index methods to confirm the validity of the index, the tags, etc. It all comes back ok. But when it hits the a_tbl.range_add(), the function reports the error that the index is not open.

      Other data points - I ftp'd the database files from the server to my dev system, reindexed on the development system and ftp back to the server (several times). I do this all the time and I have never seen this problem, but could this be causing a problem with the indexes? I am also wondering if I am doing something wrong that was forgiven or automatic in v8 and now it is in error. Failing on the .a5w page on either server really throws me. thanks for any ideas as I am really stuck on this one,
      Ken

      Comment


        #4
        Re: "open index" error after tbl.range_add() V9

        I've been looking for evidence that the problem is "alias resolution". There was a change in V9 publshing in this area. I can't tell if that is it, but look at the page in a browser, server not local, and see if you find the text "[PathAlias.ADB_Path]". If so, drop back to V9 > View > Settings > Preferences > Web Publishing > Alias Resolution and toggle it to Publish Time. Then republish that page and test. I can't tell if that is the problem, but there are a few clues that it might.
        Steve Wood
        See my profile on IADN

        Comment


          #5
          Re: "open index" error after tbl.range_add() V9

          Steve,
          Thanks, I already have resolution set to at publish time and have viewed the files using a text editor and this is not a problem. I have installed Alpha 5 V9 on the remote virtual server and found that running the script in interactive mode ON THE SERVER (using the exact same data files) does NOT fail. This suggests that the problem rests with operation while running the Alpha 5 V9 Webserver. For some reason I suspect that the index file open fails when the database file opens. I have a question - are there any issues with a short time (Y) field being indexed? This is the only thing out of the ordinary in my table. This is so bizarre. thanks,
          Ken

          Comment


            #6
            Re: "open index" error after tbl.range_add() V9

            I give. I could never figure it out - I wasted a good part of a day. I simply switched to using a query instead (15 minutes fo effort) and it works fine. Thanks,
            Ken

            Comment

            Working...
            X