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

"IF" Statement Help

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

    #16
    Re: "IF" Statement Help

    Rich:
    Just read the first post and either something is missing or you are using if() when you shouldn't:
    If Transaction Code = "A," then Date Flagged = Date(), or
    if Transaction Code = "D", then Date UnFlagged = Date()
    Both conditions produce the same result: date() !!

    On reading further on what you wish to accomplish:
    I need the Date_Flagged field to show the current date when "A" (for add) is placed in the Transaction field, and that date can stay there, and at a later date, when the Transaction Code is changed to "D" (for delete)
    You could do that several ways. If you want to use the field rules:
    In Data entery, use Conditional default value and in the window in Default put: date() and in the condition put: Date_Flagged="A".or.Date_Flagged="D".

    Comment


      #17
      Re: "IF" Statement Help

      Richard,

      Try changing your code to
      Code:
      Select 
          Case MasterList->Transaction_Code = "A"
             Masterlist->Entrydate = date()
          Case MasterList->Transaction_Code = "D"
              Masterlist->DateUnFlagged = date()
      End Select
      If it still doesn't work then try putting the code in the OnWrotefield field event.

      If it still doesn't work try putting the following in the CanWriteField field event.
      Code:
      Select 
           Case A_FIELD_VALUE.value = "A"
              Masterlist->Entrydate = date()
           Case A_FIELD_VALUE.value = "D"
               Masterlist->DateUnFlagged = date()
       End Select
      If it still doesn't work post us a sample to work with. :)

      Good Luck

      NOTE: While in field rules if you place code in a record event it doesn't matter which field you are on because the event applies to the whole record. However when placing code in a field event make sure you are on the field that you want to trigger the code.
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


        #18
        Re: "IF" Statement Help

        Tim,

        Thanks---I can see your point for the most part (just have to think about it more to actually get it straight in my head now!).


        Rich,
        Tim is the goto guy here I think (or G, or MikeW, or...)--sometimes I stick my 2 cents in when I maybe shouldn't!! :) I was simply giving a possible alternative and doesn't look look like it actually was a viable one after all.
        Please listen to them as I do when trying to learn things.




        Mike
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #19
          Re: "IF" Statement Help

          Okay Tim, I followed this code:

          Select
          Case MasterList->Transaction_Code = "A"
          Masterlist->Entrydate = date()
          Case MasterList->Transaction_Code = "D"
          Masterlist->DateUnFlagged = date()
          End Select

          ... and placed it in the CanWriteField and now it works fine.

          I appologize for the confusion earlier. I've only had experience with using expessions in Field Rules as basically one line code, and didn't realize there were so many other ways to get the same end results. I've never placed code in the Events tab before, so this has certainly been a learning experience for me.

          Once again, thanks to all who made suggestions. This message board is a lifesaver. It allows me to learn something new every day.
          Sergeant Richard Hartnett
          Hyattsville City Police Department
          Maryland

          Comment


            #20
            Re: "IF" Statement Help

            Rich:
            Have you tried any of the other suggestions?
            Did any of them work?

            Comment


              #21
              Re: "IF" Statement Help

              No I didn't. Once I found one that worked, I stuck with that. Had to keep the project moving.

              One day ........................ if I ever catch up with all my ongoing projects .......... I'll have time to just "play and experiment." LOL
              Sergeant Richard Hartnett
              Hyattsville City Police Department
              Maryland

              Comment

              Working...
              X