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

    #16
    Re: Calculated Field With a Lookup

    Alli, for future reference. This message board is divided into sections (forums). There's a separate "forum" for desktop applications. You've posted to a "forum" aimed at folks who are using the "Web application Server". If you post in the Version 11 Desktop Applications forum instead your questions will get better exposure.

    Comment


      #17
      Re: Calculated Field With a Lookup

      The lookup is set up in field rules for the table for that exact reason

      Originally posted by Tom Cone Jr View Post
      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


        #18
        Re: Calculated Field With a Lookup

        this did not work

        Originally posted by johnkoh View Post
        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


          #19
          Re: Calculated Field With a Lookup

          I thought I went to the desktop one. oops

          Originally posted by Tom Cone Jr View Post
          Alli, for future reference. This message board is divided into sections (forums). There's a separate "forum" for desktop applications. You've posted to a "forum" aimed at folks who are using the "Web application Server". If you post in the Version 11 Desktop Applications forum instead your questions will get better exposure.

          Comment


            #20
            Re: Calculated Field With a Lookup

            Alli,

            The lookup is set up in field rules for the table for that exact reason
            Does the lookup field rule autofill the bookmap, page and lot fields in the current record from corresponding fields in the source (lookup) table?

            Is the lookup field rule defined for the "calc" field, and is it supposed to autofill that field, also?

            Comment


              #21
              Re: Calculated Field With a Lookup

              Alli,

              this did not work
              Show me what ever you done and Do you know why?

              Because of this?
              book_page_lot.jpg

              did not show on your form or browse after changed the calculated value.

              Comment


                #22
                Re: Calculated Field With a Lookup

                Alli,

                In desktop applications Alpha blocks user changes to fields for which calc field rules have been defined for the table.

                In your case you've defined the calc expression in the form, instead.

                Nevertheless I think you're confusing Alpha with the lookup field rule defined for the field at the table level.

                May I suggest a work around for you?

                Why not add a field to your table structure. Define a calc field rule for the new field, but NOT a lookup rule. Instead, define a table lookup field rule for one of the fields you're using in your calc expression. Autofill the fields used in the calc expression, but NOT the calc field itself.

                Comment


                  #23
                  Re: Calculated Field With a Lookup

                  once the lot bookmap and page are populated I need it to calculate the other field and then the other field pulls in lot bookmap page and like 9 other fields. it doesnt pull in the field the calculation is on though.

                  Originally posted by Tom Cone Jr View Post
                  Alli,



                  Does the lookup field rule autofill the bookmap, page and lot fields in the current record from corresponding fields in the source (lookup) table?

                  Is the lookup field rule defined for the "calc" field, and is it supposed to autofill that field, also?

                  Comment


                    #24
                    Re: Calculated Field With a Lookup

                    calc.PNGlookup.PNG

                    When I changed it, it didnt work. I have the calculation only on the from. I cannot put the calculation in the field rules and have a lookup in the field rules. I dont understand why it quit working


                    Originally posted by johnkoh View Post
                    Alli,



                    Show me what ever you done and Do you know why?
                    This is what I have...




                    Because of this?
                    [ATTACH=CONFIG]36835[/ATTACH]

                    did not show on your form or browse after changed the calculated value.

                    Comment


                      #25
                      Re: Calculated Field With a Lookup

                      The field is not a 'calc' field per say. its a field that is in the table that needs to be calculated. If that makes sense


                      Originally posted by Tom Cone Jr View Post
                      Alli,

                      In desktop applications Alpha blocks user changes to fields for which calc field rules have been defined for the table.

                      In your case you've defined the calc expression in the form, instead.

                      Nevertheless I think you're confusing Alpha with the lookup field rule defined for the field at the table level.

                      May I suggest a work around for you?

                      Why not add a field to your table structure. Define a calc field rule for the new field, but NOT a lookup rule. Instead, define a table lookup field rule for one of the fields you're using in your calc expression. Autofill the fields used in the calc expression, but NOT the calc field itself.

                      Comment


                        #26
                        Re: Calculated Field With a Lookup

                        The field that is calculated as is the field that matches to another table to use the lookup.

                        Comment


                          #27
                          Re: Calculated Field With a Lookup

                          maybe a value recently added to the data base confusing the look up .. you are saying that it was working fine .. so either that or let me ask you if you updated your alpha recently maybe they changed some methods of calculating variables ...

                          first , when this error show up .. in date and time .. check recent records and try to copy last records some where and start checking or deleting ...

                          or uninstall the recent updated alpha ...

                          i hope this works for u
                          To live anywhere in the world today and be against equality because of race or color is like living in Alaska and being against snow.�

                          - William Faulkner

                          Comment


                            #28
                            Re: Calculated Field With a Lookup

                            oh and try to re-index your dbf tables also ... >.<
                            To live anywhere in the world today and be against equality because of race or color is like living in Alaska and being against snow.�

                            - William Faulkner

                            Comment


                              #29
                              Re: Calculated Field With a Lookup

                              I think I have it. I tried creating an actual calculated field not in my table and it seems to be working. Thanks

                              Comment

                              Working...
                              X