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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Complex conditional lookup

Collapse
X
Collapse
 
  • Page of 6
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 3 4 5 6 template Next
    #76
    Re: Complex conditional lookup

    Mike -

    This is incredible. It does just what I wanted. I have to really pull things apart to see how I can fit it in with the over all scheme of the rest of what I've done. Can't have one great looking piece and the rest only mediocre don't you know. Back to the drawing board and the books to see what I can learn.



    Everyone -

    You guys have all been great - I really appreciate all the comments and banter back and forth. It has served to show me several things.
    1. I have a lot of learning to do.

    2. There are about 6 ways from Sunday in the way you can accomplish something in Alpha 5.

    3. The Alpha Community is the best - bar none - when it comes to helping each other out. I only hope I can get to the point where I can start contributing answers instead of just asking questions.

    Comment

      #77
      Re: Complex conditional lookup

      That's a nice implementation, Mike. I actually like this one better than some of your other ones - even better than your airplane one (although I loved the plane graphics). Clean interface comes to mind. One minor point, though. You have middle name required. Some people don't have 'em, some people don't like to use 'em. But nice job.
      Peter
      AlphaBase Solutions, LLC

       [email protected]
      https://www.alphabasesolutions.com

      Comment

        #78
        Re: Complex conditional lookup

        Originally posted by Peter.Greulich View Post
        That's a nice implementation, Mike. I actually like this one better than some of your other ones - even better than your airplane one (although I loved the plane graphics). Clean interface comes to mind. One minor point, though. You have middle name required. Some people don't have 'em, some people don't like to use 'em. But nice job.

        Thanks!
        Yeah. It's a passive aggressive thing with me. Mike is my middle name. I don't use my first name. And actually I work with 2 others that do the same. In fact, I believe the figure is about 4-6% of men don't use their first names. I awefully bestowed that upon my son, too. In all my applications that have customers, clients, contacts, staff, etc, I aways have a fourth field for a common name/nickname, so the formal name and the common names are achievable.
        Mike W
        __________________________
        "I rebel in at least small things to express to the world that I have not completely surrendered"

        Comment

          #79
          Re: Complex conditional lookup

          Similar Headache?

          I would like to enter one of 12 values automatically, rather than via a lookup!

          The twelve values are bank month codes CH01, CH02, CH03....TO....CH12.

          CHO1 Would be deposits or withdrawals occurring in the month of January
          CH12 would be deposits or withdrawals occurring in the month of December

          How might I automatically insert a bank code value in the bank code field based on a pre-entered date value in either a deposit date or a payment date field ???

          Bank code field cannot be an unchangeable calculated value.
          For example "CH03" may 'later' need to be changed to "CH04", if a check written in March clears the bank in April.


          John Linley

          Comment

            #80
            Re: Complex conditional lookup

            How about a form OnSave event with:
            Code:
            parentform:[COLOR="red"]bank_month_code[/COLOR].value ="CN"+left(convert_type(parentform:[COLOR="Red"]datefield[/COLOR].value,"c"),2)
            in red would be what your field names are.
            Mike W
            __________________________
            "I rebel in at least small things to express to the world that I have not completely surrendered"

            Comment

              #81
              Re: Complex conditional lookup

              Keith:

              A different lookup question. Is it possible to automatically post (insert) a value based on a date? I have a checking account set which collects deposits and withdrawals from other tables. On the withdrawal side, when entering check data prior to printing the checks, a table lookup offers twelve bank codes, one for each month or checking period. The codes are "CH01" FOR Jan TO "CH12" FOR Dec. When entering the check date, Say today: { 08/10/2009}, I would like an automatic entry into the bank code field "CH08". What I have now is a lookup which displays the twelve bank codes, and we have to scroll to August.

              If someone has two or three separate bank accounts, the scroll list could be 24 or 36 instead of 12.

              I would need it not to be a calculated field, as it might have to be changed at a later date. For example, if a check previously assigned the August code "CH08" but does not clear the bank until Sep, the bank code would need to be changed to "CH09".

              Hope you notice this post and can help.

              Regards,

              John LInley

              Comment

                #82
                Re: Complex conditional lookup

                Originally posted by john linley View Post
                I would need it not to be a calculated field, as it might have to be changed at a later date.
                Not sure, but it could be a calc field. If, for example, you have a date field called cleared_date, and the calc field based upon that field, the calc field would update whenever you change the cleared_date field. Otherwise, with xbasic you can do anything that you need to.
                Peter
                AlphaBase Solutions, LLC

                 [email protected]
                https://www.alphabasesolutions.com

                Comment

                Previous 1 3 4 5 6 template Next
                Working...
                X