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

Field Rule size limit

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

    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

    #2
    RE: Field Rule size limit

    I ran into the same problem recently. Luckily I was able to solve my problem by removing a few blank spaces.

    The expression is limited, as I recall, to 1023 characters. However, your's seems to only have 962. (Hint: Cut and paste your expression into something like Word and let Word do a character count on it.)

    There are two ways to get around this that I know of. Actually, they are both variations of one method - call a user defined function (UDF).

    If your path was longer, you could replace the path with A5.get_path() and add the backslash before the file name. For example: , A5.Get_path()+"\xacndata".

    NOTE: This would be much better than hard-coding the current path into your expression because it would then be portable.

    Considering what you have, it looks like a more comprehensive UDF will be required. Without going into great detail to check everything, it looks like you will have to pass the values for
    ACCOUNT_TYPE, COM_EST_MO_USE, and CC_INTERSTATE_MIN
    to the function. The function itself would basically be a SELECT ... END SELECT statement something like: (I added some extra line feeds since I'm not sure how it will wrap.)

    FUNCTION My_Acct_Type_Func as N(account_type as C, com_est_mo_use as N(??), cc_interstate_min as N )

    SELECT
    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

    CASE 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

    CASE ACCOUNT_TYPE="Residential".AND.CC_INTERSTATE_MIN
    etc., etc.

    END SELECT

    My_Acct_Type_Func = Account_type

    END FUNCTION

    Comment


      #3
      RE: Field Rule size limit

      Note: I'd still change d:/a5v5/ to A5.get_path() so it will be more portable.

      You could probably also create a global variable with a short name and set that variable equal to the value of the path + table name:
      Pnam = a5.get_path()+"\xacndata.dbf"

      I haven't actually tried this so I don't know for sure that it works.

      Comment


        #4
        RE: Field Rule size limit

        Cal,

        Thanks for the tips. I hadn't thought of the portability factor. I'll make sure to incorporate it in the code.

        Phil

        Comment

        Working...
        X