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

Problem with lookup in line detail

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

    Problem with lookup in line detail

    Hi,

    I think I have a unique problem, and can't figure out how to handle it.

    The invoice header section is standard -- invoice #, customer #, date, etc. However, the product lookup in the line detail section is causing headaches. Specifically, I need to be able to do a lookup that restricts the products shown in the lookup based on the customer number. Each customer has an assigned group of inventory they can purchase, based on customer number (each produt code starts with the customer number).

    I'm a newbie who is trying to learn fast, but this roadblock has me stumped. I'm not sure if I am indexing things properly or what, and am not sure what to do in the lookup section of the field rules to get this to happen. Any help would be appreciated.

    #2
    A simple way to do it would be if you add the customer id field to the invoice items table
    And put this script on the �OnEnterRecords� events
    Code:
    t1 = table.get("invoice_header")
    t2 = table.get("invoice_items")
    t2.Customer_Id = t1.Customer_Id
    And then add this filter to the lookup for the product id
    Code:
    left(Product_Id,len(invoice_items->customer_id))=invoice_items->customer_id
    Daniel Weiss
    EZ Link Software

    Comment


      #3
      Thanks Dan -- I'll try that out tonight!

      Comment


        #4
        filter your table lookup

        You can also use a filter in the field rules:

        http://support.alphasoftware.com/alp...d_Lookups).htm

        Good luck
        Cheryl
        Cheryl
        #1 Designs By Pagecrazy
        http://pagecrazy.com/

        Comment


          #5
          Problems with the filter

          Hi Dan,

          The first part of the equation worked great. The customer Id fills in on the detail just fine. Let me explain what is going on now;

          First, to simply my original question, I framed it as a typical invoice situation.

          Actually, it's similar but a different application - These are timecards that are entered in on a weekly basis. The "cards" are the same as an invoice. The detail is the time for each employee (the customer). Each employee has a variety of jobs they perform, each of which has a different pay rate. There is a table which contains the employee number, the code for the job, and a rate. This table is the "products" table.

          So, each "invoice" (or paycard) has multiple jobs entered for the employee,
          with multiple line items.

          I've got the set defined as follows: The header is the parent, with the detail as a one-to-many child with referential integrity. The paycode table (products) is a child of the detail, one-to-one. When I go to setup the lookup for the detail paycode, I have the paycode table as the lookup, with the linking field being the paycode #. However, when I create the filter, the expression builder only shows me fields from the lookup table... it won't let me enter in the matching field from the detail....

          Do I have the set configured wrong, or do I need to define other keys? Thanks for any other insight you can give me.

          Comment


            #6
            try this: paycode=cards->paycode

            Shawn,

            Try this for your filter: paycode=cards->paycode

            paycode is field name in lookup table

            cards-> table name of header/parent table you are doing the lookup from
            paycode is field name in the table you are doing the lookup from

            Hope that makes sense.

            Cheryl
            Cheryl
            #1 Designs By Pagecrazy
            http://pagecrazy.com/

            Comment


              #7
              Great

              Cheryl & Daniel -- Thanks so much! The combination of your efforts has solved this problem, and I'm on to the next! I appreciate your kind efforts! Alpha has a lot more going for them than just their software -- the users who are so helpful in this forum!

              Comment

              Working...
              X