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 Help -- having a mental block on lookup()

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

    Field Rule Help -- having a mental block on lookup()

    Hi,
    I'm having a mental block with writing a field rule. I have a field in a table called pfl-detail that needs to show the period name, using a lookup to the gl_periods dbf file. I used my expression that works to find the 'Current' period as a guide to get the period name based on the doc_date field.

    For example, the gl_periods dbf contains rows with the following fields pertaining to the period record:

    period_name, period_year, start_date_dt, end_date_dt

    I need to populate the pdnm field in table pfl-detail based on the date contained the doc_date.

    Here is what I have tried that doesn't work:

    LOOKUP("gl_periods.dbf","dtos(Start_Date_Dt)>=dtos(doc_date).and.dtos(End_Date_Dt)<=dtos(doc_date)","Period_Year")

    I used this code as a guide :
    LOOKUP("gl_periods.dbf","dtos(Start_Date_Dt)<=dtos(date()).and.dtos(End_Date_Dt)>=dtos(date())","Period_Year") /*returns the current period year*/

    I'm sure this will be an easy one for somebody, but I can't seem to figure it out.

    Hope someone can help me! Thanks!
    Land of the Free, Because of the Brave
    Support our US Military

    #2
    Re: Field Rule Help -- having a mental block on lookup()

    Your guide expression works because Alpha knows to evaluate date(). You modified expression doesn't work because Alpha doesn't know how to handle doc_date.

    Looks like I misread the data type on doc_date.

    Code:
    doc_date = {11/15/2010}
    
    ? "dtos(Start_Date_Dt)>=dtos({"+dtoc(doc_date)+"}).and.dtos(End_Date_Dt)<=dtos({"+dtoc(doc_date)+"})"
    = "dtos(Start_Date_Dt)>=dtos({11/15/2010}).and.dtos(End_Date_Dt)<=dtos({11/15/2010})"
    Whole expression...

    Code:
    LOOKUP("gl_periods.dbf","dtos(Start_Date_Dt)>=dtos({"+dtoc(doc_date)+"}).and.dtos(End_Date_Dt)<=dtos({"+dtoc(doc_date)+"})"
    ,"Period_Year")
    Last edited by Stan Mathews; 11-30-2010, 04:20 PM.
    There can be only one.

    Comment


      #3
      Re: Field Rule Help -- having a mental block on lookup()

      Thanks Stan. I tried your code, and still didn't work. I get 'Argument is incorrect data type' error.
      Land of the Free, Because of the Brave
      Support our US Military

      Comment


        #4
        Re: Field Rule Help -- having a mental block on lookup()

        Edited my earlier reply. I misread the data type on doc_date.
        There can be only one.

        Comment


          #5
          Re: Field Rule Help -- having a mental block on lookup()

          Tried converting everything to character. I added two fields in gl_periods; s_start_dt and s_end_dt. They are based on field rule in that table of dtos(Start_date_dt) and dtos(End_Date_dt).

          Created another field in pfl-detail called crmemodate that is dtos(doc_date).

          Edited the code as follows:

          LOOKUP("gl_periods","S_start_Dt>=crmemodate.and.S_end_dt<=crmemodate","Period_Name")

          Still doesn't work.
          Land of the Free, Because of the Brave
          Support our US Military

          Comment


            #6
            Re: Field Rule Help -- having a mental block on lookup()

            Inside of quotation marks Alpha treats variables as the text of their names, not their contents.

            "S_start_Dt>=crmemodate.and.S_end_dt<=crmemodate"

            is evaluated like

            S_start_Dt>=crmemodate

            not

            S_start_Dt>=value_of_the_variable_crmemodate


            See the edit of my earlier post.
            There can be only one.

            Comment


              #7
              Re: Field Rule Help -- having a mental block on lookup()

              Stan,
              You are the GENIUS. Thank you, that worked! I changed the code per your example, recalculated field rules, and now have the period names!
              Land of the Free, Because of the Brave
              Support our US Military

              Comment

              Working...
              X