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

Calculated Field With a Lookup

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

    Calculated Field With a Lookup

    I have a field that is calculated on the Form level and has a lookup on the table level. It was working just fine, but all of the sudden the field quit calculating. Everything looks right.
    i changed a few field rules on fields that have nothing to do with this one. and I emptied and packed the table and now it doesnt work

    Does anyone know what could have happened?

    #2
    Re: Calculated Field With a Lookup

    Alli,

    Maybe the Index problem but show your lookup expression

    Comment


      #3
      Re: Calculated Field With a Lookup

      Alli,

      Your design may be confusing Alpha Five.

      If you have a table lookup field rule for the field, why would you then also have a calculated field rule in the form... for the same field?

      Comment


        #4
        Re: Calculated Field With a Lookup

        It did work just fine. Then it stopped. The field is calculated based on 3 other fields. And it has to have a lookup on it. I am not understanding why it all of the sudden quit working.


        Originally posted by Tom Cone Jr View Post
        Alli,

        Your design may be confusing Alpha Five.

        If you have a table lookup field rule for the field, why would you then also have a calculated field rule in the form... for the same field?

        Comment


          #5
          Re: Calculated Field With a Lookup

          I dont use indexes so I dont think that it is that. What do you mean by lookup expression?

          Originally posted by johnkoh View Post
          Alli,

          Maybe the Index problem but show your lookup expression

          Comment


            #6
            Re: Calculated Field With a Lookup

            I can get it to either populate or show the look up. I had it working with both before but now it refuses to work....

            I have to have the field calculated with RIGHT('0000'+ALLTRIM(STR(BOOKMAP)),4)+RIGHT('00'+ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT) , however if i calculate it, it wont let me put a look up on it. I got it to work by putting the look up on table level and calculation on form. That was the only way I could get it to work.

            Anyone know of any other way to get this to work?

            Comment


              #7
              Re: Calculated Field With a Lookup

              Alli,

              I mean this,
              I have a field that is calculated on the Form level and has a lookup on the table level.
              How did you write for it?

              Comment


                #8
                Re: Calculated Field With a Lookup

                On the field rules I built in a lookup. not using a formula but the default way... and in the form level i went to the default section to update the field and entered in a simple default of RIGHT('0000'+ALLTRIM(STR(BOOKMAP)),4)+RIGHT('00'+ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT)

                Originally posted by johnkoh View Post
                Alli,

                I mean this,


                How did you write for it?

                Comment


                  #9
                  Re: Calculated Field With a Lookup

                  Alli, is this for a web application?

                  Comment


                    #10
                    Re: Calculated Field With a Lookup

                    Its a desktop application

                    Originally posted by Tom Cone Jr View Post
                    Alli, is this for a web application?

                    Comment


                      #11
                      Re: Calculated Field With a Lookup

                      Alli,

                      I think this

                      Code:
                      'RIGHT([B][COLOR="#FF0000"]'0000'[/COLOR][/B]+ALLTRIM(STR(BOOKMAP)),4)+RIGHT([B][COLOR="#FF0000"]'00'[/COLOR][/B]+ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT)
                      dim bookmap as n = 123456789
                      dim page as n = 789
                      dim lot as c ="abc"
                      
                      vTxt1 = right(alltrim(str(bookmap)),4)
                      vTxt2 = right(alltrim(str(page)),2)
                      vtxt3 = "0000"+vtxt1+"00"+vtxt2
                      ?vtxt3
                      = "000067890089"
                      
                      vTest = "0000"+RIGHT(ALLTRIM(STR(BOOKMAP)),4)+"00"+RIGHT(ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT)
                      ? vtest
                      = "000067890089abc"

                      Comment


                        #12
                        Re: Calculated Field With a Lookup

                        What do I do with that? I just know how to do the basic ones.

                        Originally posted by johnkoh View Post
                        Alli,

                        I think this

                        Code:
                        'RIGHT([B][COLOR="#FF0000"]'0000'[/COLOR][/B]+ALLTRIM(STR(BOOKMAP)),4)+RIGHT([B][COLOR="#FF0000"]'00'[/COLOR][/B]+ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT)
                        dim bookmap as n = 123456789
                        dim page as n = 789
                        dim lot as c ="abc"
                        
                        vTxt1 = right(alltrim(str(bookmap)),4)
                        vTxt2 = right(alltrim(str(page)),2)
                        vtxt3 = "0000"+vtxt1+"00"+vtxt2
                        ?vtxt3
                        = "000067890089"
                        
                        vTest = "0000"+RIGHT(ALLTRIM(STR(BOOKMAP)),4)+"00"+RIGHT(ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT)
                        ? vtest
                        = "000067890089abc"

                        Comment


                          #13
                          Re: Calculated Field With a Lookup

                          If you can, "C" type of field is better than "N" type for manipulate it later.

                          Comment


                            #14
                            Re: Calculated Field With a Lookup

                            Alli,

                            go back the field rule where " On the field rules I built in a lookup " , change like this "0000"+RIGHT(ALLTRIM(STR(BOOKMAP)),4)+"00"+RIGHT(ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT) instead of the old one, RIGHT('0000'+ALLTRIM(STR(BOOKMAP)),4)+RIGHT('00'+ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT)

                            Comment


                              #15
                              Re: Calculated Field With a Lookup

                              Alli, when you say you "put the lookup on table level", are you saying you go into field rules for the table and define a table lookup field rule so the user can retrieve field value(s) from a separate table in order to populate field(s) in the current record?

                              --- tom

                              Comment

                              Working...
                              X