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
Devcon 2020 Goes Virtual! LEARN MORE >

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 "not an open index" in form calc field

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Error "not an open index" in form calc field

    I have created a form for a set with the following calculated fields defined in the form:

    OpValue = if(previous("Client_id","Claclper")=Client_Id.and.previous("Acl_id","Claclper")=Acl_Id,previous("Cl_value","Claclper"),0)

    OpValAcc = if(previous("Client_id","Claclper")=Client_Id.and.previous("Acl_id","Claclper")=Acl_Id,previous("Clvalaccr","Claclper"),0)

    BaseRate = lookupn("C",EndOfPeriodID(Period_Id),"rate","baserate","Startdatex")

    BaseAdj = lookupn("C",EndOfPeriodID(Period_Id),"rate","baseadj","Startdatex")

    TCTRPC = if(lookupl("F",Trans->Txntyp_Id,"tctr","txntype","Txntyp_Id"),lookupn("f",Trans->Period_Id,"tctr","period","Period_Id"),0)

    Deals = IF(LOOKUPL("F",Trans->TXNTYP_ID,"deal","txntype","Txntyp_Id")=.F.,0,IF(LOOKUPL("F",Trans->TXNTYP_ID,"deal_pos","txntype","txntyp_id")=.T.,1,-1))*Trans->Tot_Amt

    Income = IF(LOOKUPL("F",Trans->TXNTYP_ID,"deal","txntype","Txntyp_Id")=.T.,0,Trans->TOT_AMT)*(1+calc->TCTRPC/100)

    Weighting = IF(Trans->SET_DATE=CTOD(" ").OR.LOOKUPL("F",Trans->TXNTYP_ID,"deal","txntype","Txntyp_Id")=.F.,0,(LOOKUPD("F",Trans->PERIOD_ID,"enddate","period","period_id")-Trans->SET_DATE)/DAYSINPERIODID(Trans->PERIOD_ID))

    TotDeals = total(calc->Deals,GRP->Return)

    TotInc = total(calc->Income,GRP->Return)

    WtDeal = calc->Deals*calc->Weighting

    TotCash = total(trans->Tot_Amt,GRP->Return)

    DaysInPeriod = DaysInPeriodID(Period_Id)

    CashReturn = (calc->Baserate+calc->Baseadj)*calc->Daysinperiod/365

    TotWtDeals = total(calc->Wtdeal,GRP->Return)

    IsCash = lookupl("F",Acl_Id,"Cashreturn","assetcl","Class_Id")

    NonCashReturn = if(calc->OpValue+calc->Opvalacc+calc->Totwtdeals=0,0,(Cl_Value+Clvalaccr-calc->Opvalue-calc->Opvalacc-calc->Totdeals+calc->Totinc)/(calc->Opvalue+calc->Opvalacc+calc->Totwtdeals))*100

    Return = if(calc->Iscash,calc->Cashreturn,calc->Noncashreturn)

    There seems to be a problem with the last 3 fields: when the form is in design mode and I click on Form/Calculated fields.. then click on the "NonCashReturn" line, I get a "Not an open index" error message. The "Return" field gives the following error message: "error: lookupl(F,"02",CASHRETURN,assetcl,Class_id) not an open index : Function 'if'.".

    When I open the expression builder for these calc fields, they evaluate correctly, without any error messages; they also display correctly on the form.

    I have compacted the database, rebuilt the indexes for assetcl.dbf etc. but the error messages won't go away. Although the form shows the correct values, I am worried about installing the database on the client's computer, in case it causes problems later.

    Does anyone know what is causing this problem?

    I am using build 4035/3028.

    Thanks,
    Tony
    Tags: None
    #2
    My thought is that you may have a timing/threading issue.

    The documentation states that the total (and some other) functions

    Note: This function is a report writer function, not intended for table level field rules or other expressions. While the function may perform in some areas outside of the report writer, its use there is not supported.
    It is often used successfully in the context you have of displaying a total on a form "TotDeals = total(calc->Deals,GRP->Return)". When you then compound the issue by using that calculated field in creating the expression for another calculated field, who knows?

    You also have secondary calculated fields which rely on first level calculated fields which rely on lookupl(), lookupd(), etc.

    Don't know that you are doing anything wrong, just looks like intensive calculations are happening.
    There can be only one.

    Comment

      #3
      Stan,

      Thanks for your reply. I will have a look at the way the calculations are done, to see if there is a better (i.e. less complicated) way.

      Incidentally, since sending my first message, I have tried putting the calculation of IsCash, NonCashReturn and Return into the form's OnFetch event, instead of using calculated fields, and it works OK, so perhaps this is a safer way to do it.

      Tony

      Comment

        #4
        Hi Tony,
        I stopped using all the LOOKUPx() funtions due to the index problem they always have if the index they depend on are corrupted or was dropped by A5. I now use the LOOKUP() function instead. This function does not use any index and is therefore more reliable than the LOOKUPx() which relies on index to work. Give the LOOKUP() function a try & you will have a trouble free lookups. Bye.

        RAWLINGS

        Comment

          #5
          Hi Rawlings,

          Thanks, I will have a look at lookup().

          Tony

          Comment

            #6
            Just remember that the plain Lookup() command basically runs a query. If you are doing this in a very large table, it could take a few seconds each time it runs.

            I don't know if it uses LQO (Lightning Query Optimization) but if it does then it's using an index (that's the way LQO works) and could result in bad data being returned if the index is corrupted but not missing.

            Comment

              #7
              Cal,

              Thanks, I want to avoid anything that slows the app down, so I think I will create variables and calculate their values with a script.

              Tony

              Comment

              Previous template Next
              Working...
              X