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

Field Rule size limit

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

    Field Rule size limit

    Hi,

    I am having a problem with a field rule in my table which I believe has to do with a limitation on the length of the field rule. The current field rule is as follows:

    CASE(ACCOUNT_TYPE="Commercial".AND.COM_EST_MO_USE=LOOKUPN("F","1","Com_min_use3","xacndata","Key"),LOOKUPN("F","1","Com_interstate_3","xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN>LOOKUPN("F","1","Res_break_pt","xacndata","Key"),LOOKUPN("F","1","Res_plan1_rate","xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN". Then, when I add the full path to the table references in each of the Lookup statements I get a the normal "Result: 0 Type:N" message (or equivalent depending on the calculated value) at the bottom of the large window in the Expression Builder as expected.

    So, the complete field rule (with full paths included) which is properly evaluated by A5V5 is as follows:

    CASE(ACCOUNT_TYPE="Commercial".AND.COM_EST_MO_USE=LOOKUPN("F","1","Com_min_use3","d:/a5v5/xacndata","Key"),LOOKUPN("F","1","Com_interstate_3","d:/a5v5/xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN>LOOKUPN("F","1","Res_break_pt","d:/a5v5/xacndata","Key"),LOOKUPN("F","1","Res_plan1_rate","d:/a5v5/xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN=LOOKUPN("F","1","Com_min_use3","d:/a5v5/xacndata","Key"),LOOKUPN("F","1","Com_interstate_3","d:/a5v5/xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN>LOOKUPN("F","1","Res_break_pt","d:/a5v5/xacndata","Key"),LOOKUPN("F","1","Res_plan1_rate","d:/a5v5/xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN
    Tags: None
    #2
    RE: Field Rule size limit

    Full expression is

    CASE(ACCOUNT_TYPE="Commercial".AND.COM_EST_MO_USE"LOOKUPN("F","1","Com_min_use2","d:/a5v5/xacndata","Key"),LOOKUPN("F","1","Com_interstate_1","d:/a5v5/xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Commercial".AND.COM_EST_MO_USE"LOOKUPN("F","1","Com_min_use3","d:/a5v5/xacndata","Key"),LOOKUPN("F","1","Com_interstate_2","d:/a5v5/xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Commercial".AND.COM_EST_MO_USE>=LOOKUPN("F","1","Com_min_use3","d:/a5v5/xacndata","Key"),LOOKUPN("F","1","Com_interstate_3","d:/a5v5/xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN>LOOKUPN("F","1","Res_break_pt","d:/a5v5/xacndata","Key"),LOOKUPN("F","1","Res_plan1_rate","d:/a5v5/xacndata","Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN"LOOKUPN("F","1","Res_break_pt","d:/a5v5/xacndata","Key"),IF(CC_INTERSTATE_MIN "= LOOKUPN("F","1","Res_plan2_free_min","d:/a5v5/xacndata","Key"),0,LOOKUPN("F","1","Res_plan2_rate","d:/a5v5/xacndata","Key")*(CC_INTERSTATE_MIN-LOOKUPN("F","1","Res_plan2_free_min","d:/a5v5/xacndata","Key"))))

    Is there a limit to the size of a field rule? - 1024 characters

    If so, is there any known work around to help me out in this circumstance? Shorter field names... "RP2Rt" vs "Res_plan2_rate" saves nine characters per usage.

    You might establish a global variable, character, name lktbl, value "d:\a5v5\xacndata" and rewrite as

    CASE(ACCOUNT_TYPE="Commercial".AND.COM_EST_MO_USE"LOOKUPN("F","1","Com_min_use2",lktbl,"Key"),LOOKUPN("F","1","Com_interstate_1",lktbl,"Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Commercial".AND.COM_EST_MO_USE"LOOKUPN("F","1","Com_min_use3",lktbl,"Key"),LOOKUPN("F","1","Com_interstate_2",lktbl,"Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Commercial".AND.COM_EST_MO_USE>=LOOKUPN("F","1","Com_min_use3",lktbl,"Key"),LOOKUPN("F","1","Com_interstate_3",lktbl,"Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN>LOOKUPN("F","1","Res_break_pt",lktbl,"Key"),LOOKUPN("F","1","Res_plan1_rate",lktbl,"Key")*CC_INTERSTATE_MIN,ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN"LOOKUPN("F","1","Res_break_pt",lktbl,"Key"),IF(CC_INTERSTATE_MIN "= LOOKUPN("F","1","Res_plan2_free_min",lktbl,"Key"),0,LOOKUPN("F","1","Res_plan2_rate",lktbl,"Key")*(CC_INTERSTATE_MIN-LOOKUPN("F","1","Res_plan2_free_min",lktbl,"Key"))))

    possibly do the same with the field names.

    There can be only one.

    Comment

      #3
      RE: Field Rule size limit

      Stan,

      This sounds plausible and I am going to give it a try. One problem though. I know how to dim and fill a Global variable via Xbasic, how and where would you suggest I dim and fill the one you suggest here?

      Phil

      Comment

        #4
        RE: Field Rule size limit

        To have it available when needed I would suggest either in the autoexec script or in the oninit event of your startup form.
        There can be only one.

        Comment

          #5
          RE: Field Rule size limit

          Depending on your structure you might want to go with

          a5.get_path() in place of

          "d:/a5v5/xacndata"

          Try

          ? a5.get_path() in the interactive window to see what you get.

          It might be even easier to move "xacndata" into the proper directory so you don't need the drive letter and path specification.....


          Lookup_Table
          The name of a table. Lookup_Table can include a full drive and path specification. If you omit the drive and path, Alpha Five searches the directory of the current table. - (I believe this should read "current database")
          There can be only one.

          Comment

            #6
            RE: Field Rule size limit

            Another option would be to make your own function that did all of the things you need, then simply execute the function in the field rule.

            - Steve
            -Steve
            sigpic

            Comment

              #7
              RE: Field Rule size limit

              Stan,

              Thanks you for the clarification and definitions.

              I got the problem resolved, and it turned out I didn't need to use variables to do it. It seems that in each field rule that used a lookup statement of whatever flavor I had to place the complete path in front the table reference in either the first lookup statement or both the first and second lookup statements.

              The only thing I can think is that a complete path reference needs to reside at least once in each field rule with a lookup table statement. Why this works, I don't know. But, like many times working with code, if it works don't question it, just use it.

              So, thanks for the tips. They were just wat I needed to get "over the hump" and get this thing working.

              Cheers,
              Phil

              Comment

              Previous template Next
              Working...
              X