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

Not an open index Error

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

  • markbwillard
    replied
    Re: Not an open index Error

    THANKS STAN!!!!! Geatly appreciate it!

    I will post a video screencast when I see the brosew jumps around with the data.

    Leave a comment:


  • Stan Mathews
    replied
    Re: Not an open index Error

    1) (freight) LOOKUPN("L",LOOKUPN("F",ITEMS,"id","merchandisedetails","sku"),"freighttotal","merchandisepricechange","id")
    The merchandisedetails table has index tagnames ID and PID. It does not have an index tagname sku.

    LOOKUPN("F",ITEMS,"id","merchandisedetails","sku") this portion is failing due to there not being a necessary sku index.

    I do not experience any browse jumping around.

    Leave a comment:


  • markbwillard
    replied
    Re: Not an open index Error

    Hi Stan:

    Here is the sample (attached). OPen merchandise form. On that form you will see package browser.

    Other question not related to this.

    When I enter data on the top browse I see the flips around few time.

    Thanks. Mark
    Attached Files

    Leave a comment:


  • Stan Mathews
    replied
    Re: Not an open index Error

    Time to attach a sample workspace for diagnosis.

    Enter must begin first.

    http://msgboard.alphasoftware.com/al...ht=enter+begin

    Leave a comment:


  • markbwillard
    replied
    Re: Not an open index Error

    And,Yes! "Sku" and Id exists! I think there is something really wrong. Also, what is this error?
    Attached Files

    Leave a comment:


  • markbwillard
    replied
    Re: Not an open index Error

    Hi Stan:

    I have followed exactly like you did in this example before!

    http://msgboard.alphasoftware.com/al...ex+calculation

    Leave a comment:


  • Stan Mathews
    replied
    Re: Not an open index Error

    LOOKUPN("L",LOOKUPN("F",ITEMS,"id","merchandisedetails","sku"),"freighttotal","merchandisepricechange","id")
    This expression relies on an index tagname sku in the merchandisedetails table and an index tagname id in the merchandisepricechange table. Are those still present? Have you updated the indexes in both tables?

    Leave a comment:


  • markbwillard
    replied
    Re: Not an open index Error

    Hi Stan:

    It worked yesterday! Just started to happen this morning.

    Here is my overall screenshot!

    Mark
    Attached Files

    Leave a comment:


  • Stan Mathews
    replied
    Re: Not an open index Error

    The final parameter in lookupn() is the index name, seems you have the third parameter as the index name.

    You've shown the screen shot of the index builder for the package table. None of those lookupn() expressions above have anything to do with the package table.

    Leave a comment:


  • markbwillard
    replied
    Re: Not an open index Error

    1) (freight) LOOKUPN("L",LOOKUPN("F",ITEMS,"id","merchandisedetails","sku"),"freighttotal","merchandisepricechange","id")
    2) (landingcost) LOOKUPN("L",LOOKUPN("F",ITEMS,"id","merchandisedetails","sku"),"lndcost","merchandisepricechange","id")
    3) (margin field) LOOKUPN("L",LOOKUPN("F",ITEMS,"id","merchandisedetails","sku"),"Margin","merchandisepricechange","id")
    4) (cost field) LOOKUPN("L",LOOKUPN("F",ITEMS,"id","merchandisedetails","sku"),"Retail","merchandisepricechange","id")

    Leave a comment:


  • Stan Mathews
    replied
    Re: Not an open index Error

    Tis hard to tell from your screen shot of the lookupn() error. The error reporting sometimes doesn't indicate the true expression being used. You screen shot shows an expression at odds with the syntax for lookupn() where all paramters should be quoted. Using the documentation example.......

    lookupn("F", CUST_ID, "BALANCE", "c:\databases\CUSTOMER.DBF", "CUSTOMER_ID")

    The second parameter in the example is not quoted in the example as the value in CUST_ID is being passed to the function.
    The full path to the table is not necessary if the table is part of the current workspace.


    So what is your actual lookupn() expression?

    Leave a comment:


  • markbwillard
    started a topic Not an open index Error

    Not an open index Error

    I am getting this erro when I am trying to use lookupn() function. It used to work but now it does not. I check if I had the index defined correctly, and it looks like I do.

    Here are the screenshot.


    Thanks for the help!
    Attached Files
Working...
X