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



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

rules field look up problem

  • Filter
  • Time
  • Show
Clear All
new posts

  • rules field look up problem

    i have a look up where i fill multiple fields on a form

    fill from lens.dbf to fields on form
    look up in NAME field
    lens -> name
    tint -> tint_type
    ar-> anti_reflex

    the lens to name fills properly

    the tint_type and ant_refex are filled with the previous tint and ar look up??

    then if i click on the lens a second time they all load properly

    thanks in advance

  • #2
    Re: rules field look up problen


    Sorry, I did not understand about your problem. Are you looking for some lookup condition?


    • #3
      Re: rules field look up problen


      its a simple look up

      click on lens field in form --list of lenses drops down
      click on name of lens
      look up puts name into name field and tint into tint field and ar into ar field
      on first click the name field ins filled with the name i clicked on
      however the tint and ar fields are filled with the tint and ar that i had previously clicked and entered in the tint and ar field on the previous record on in the previous record


      • #4
        Re: rules field look up problen

        tell us about the other field rules you have in place for both the

        tint field and
        ar field


        • #5
          Re: rules field look up problem


          Show us more detail.


          • #6
            Re: rules field look up problem

            both those fields also have a look up in the rules look up to select a different tint,ar than is on the lens.dbf
            then when the fields (lens,tint,ar) is filled there are rules that fill in the price and vcode
            which works only after i click on the lens a second time and the correct lens, tint and ar are filled into the fields on the form


            • #7
              Re: rules field look up problem


              I am still learning A5 and got a lot of help from this forum. Specially, Tom, Stan, Mike and all of forum users.

              Do not hesitate or be shy about your detail. show all of the materials, such as table info, your code or screenshots.
              So those folks will understand your problem.


              • #8
                Re: rules field look up problem


                I suspect the additional field rules for the tint and AR fields are causing the problem. Either stop auto-filing from the Lens lookup, or disable the separate lookup rules for tent_ar.


                • #9
                  Re: rules field look up problem

                  You might be able to have a table level field rule to fill the fields as you do now

                  look up puts name into name field and tint into tint field and ar into ar field
                  Then have a form level lookup to allow the user to override the default choices made by the table level rule.
                  There can be only one.


                  • #10
                    Re: rules field look up problem

                    sorry for delay working
                    i have had it fill into field with no rules and it still fills with the previous fields
                    it's like the lens tint ar are saved in a variable then that is filled on second click the info from the dbf is filled

                    will try to load screen shots


                    • #11
                      Re: rules field look up problem


                      A useful debugging technique is to run the "default" form for the set supporting your form. This is the "default" form that alpha will build for you.

                      If the form behaves correctly that's a good sign there is no trouble in your field rules, so the trouble must lie in your custom form.

                      If the "default" form misbehaves then its a good sign the trouble lies in your field rules.


                      • #12
                        Re: rules field look up problem

                        hope these big enough to see

                        rules fill blens.dbf from dropdown to form

                        Attached Files


                        • #13
                          Re: rules field look up problem

                          with default form i get no records in to display
                          by removing filter it works


                          • #14
                            Re: rules field look up problem

                            thanks stan have not used that before

                            now how to get the filter to work
                            i'll work on it


                            • #15
                              Re: rules field look up problem

                              with default form i get no records in to display
                              by removing filter it works
                              Interesting statement. Puzzling, but interesting.

                              Filter mentioned for the first time ? Why would the default form have a filter ?

                              And then, ... "... it works". Curious expectations here. While "... it works" makes sense to you, try to imagine how difficult it is for us to grasp your meaning. We have no way to know what (or which) "it" you are referencing, nor do we know what "works" might mean. How about furnishing more details, and a sample of the database itself?