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

Conditional Look Up on a Calculated Field

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

  • #16
    Re: Conditional Look Up on a Calculated Field

    Ray, if you ignore the punctuation I think Alli is saying:

    if deedtype is "cl" or "i" populate the buyer and propaddr fields

    if deedtype is anything else populate the seller and propaddr fields

    if elook2 doesn't match elook in the lookup source table don't populate anything

    However, I don't see a "Buyer" field and I don't see a "Seller" field anywhere in the data or on the Deed2 form.

    I've asked Alli to use actual field names twice, but ...

    Will wait to see if Alli can clarify further.

    Comment


    • #17
      Re: Conditional Look Up on a Calculated Field

      Phew!

      Comment


      • #18
        Re: Conditional Look Up on a Calculated Field

        Pretty close. The lookup will only find on a perfect match I guess is what i am trying to say.

        CL and L need to fill buyer and address anything other than those two need to fill seller and address... The mapping on the lookup (i think thats what its called) need to be conditional. I am trying to accomplish having this happen with just one lookup.

        I appreciate you working with me and trying to help.

        Originally posted by Ray in Capetown View Post
        I will give this a shot

        The elook2 field is calculated
        =elook2 is a calc field,
        based on what is keyed into lot bookmap and page,
        =that is made up from from a combination of fields named lot bookmap and page,
        once that is calculate I need a lookup off the elook. the elook is populated with RIGHT('0000'+ALLTRIM(STR(BOOKMAP)),4)+RIGHT('00'+ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT) .
        This look up will fill in the buyer and address fields with the buyer and propaddr fields from the look up.

        =then I need to lookupanother field, elook, made up of bookmap+page+lot (from another table?) and return a name an address that go into "buyer" and "address" fields
        if the deedtype field is cl or l .
        = if the type field contains either "cl"or "i"
        it will fill in the seller and propaddr fields from the look up table with buyer and addr fields
        =then it will fill in the seller and propaddr fields

        Is that so far on the right track?

        then...
        if the deedtype field is anything other that cl or l. The elook field matches exactly with the elook in the lookup table if not nothing gets pulled in.
        What does that mean?

        Comment


        • #19
          Re: Conditional Look Up on a Calculated Field

          Alli,

          This is my last post unless you start using actual field names in your replies. What is the "buyer" field name in your table ? what is the "seller" field name in your table ?

          Comment


          • #20
            Re: Conditional Look Up on a Calculated Field

            buyerfirst buyerlast and buyercode in deed need to be filled with buyerfirst buyerlast and buyercode from mari if the deedtype is CL or L

            selerfirst selerlast and selercode in deed need to be filled with buyerfirst buyerlast and buyercode from mari if the deedtype is NOT CL or L


            Originally posted by Tom Cone Jr View Post
            Alli,

            This is my last post unless you start using actual field names in your replies. What is the "buyer" field name in your table ? what is the "seller" field name in your table ?

            Comment


            • #21
              Re: Conditional Look Up on a Calculated Field

              Thanks, that's clear.

              When do you want this lookup to occur?

              a) during entry of a new record only?

              b) whenever the value in elook2 field changes?



              Is the user permitted to make changes to the "buyer" or "seller" or "address" fields by hand ?

              Comment


              • #22
                Re: Conditional Look Up on a Calculated Field

                It is in an entry form so typically it will be a new record. The only time it would be if it changes is if it is miss keyed originally.

                I think it would be safe to say during a new entry only, when the elook2 field is calculated

                There is a Match field that they have to enter and depending on what they enter is whether they have access to change it or not.

                They can always manually change the buyer and the address fields

                If they enter a 1 in the match field they can manually change everything, if they enter a 2 they can manually change everything other than the seller fields.


                Originally posted by Tom Cone Jr View Post
                Thanks, that's clear.

                When do you want this lookup to occur?

                a) during entry of a new record only?

                b) whenever the value in elook2 field changes?



                Is the user permitted to make changes to the "buyer" or "seller" or "address" fields by hand ?

                Comment


                • #23
                  Re: Conditional Look Up on a Calculated Field

                  Ok, thanks.

                  I'll give the scenario some thought over the weekend. Not sure a table lookup field rule is the best way to go...

                  Comment


                  • #24
                    Re: Conditional Look Up on a Calculated Field

                    Alli, I guess I spoke too soon.

                    Cannot find fields "buyerfirst, buyerlast, buyercode, selerlast, selerfirst, or selercode" in the deed table. What am I missing?

                    Comment


                    • #25
                      Re: Conditional Look Up on a Calculated Field

                      After I left work on Friday I realized that I changed the field names.... The buyer fields are Granteefir, Granteelas & Granteecod and the seler fields are grantorfir grantorla and grantorcod

                      sorry

                      Originally posted by Tom Cone Jr View Post
                      Alli, I guess I spoke too soon.

                      Cannot find fields "buyerfirst, buyerlast, buyercode, selerlast, selerfirst, or selercode" in the deed table. What am I missing?

                      Comment

                      Working...
                      X