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

Another calculated lookup field rule problem

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

    Another calculated lookup field rule problem

    I think I am getting brain dead. I am again stuck on a field rule lookup and need help. I would so appreciate any help provided on my latest problem. Here's the issue:

    Table = Inspections (master table in a one-to-many set)
    Field to be filled = LastDtChecked (date field)
    Lookup Field = DateChecked (user entered) (date field)
    Location field = user entered (numeric)
    InspectionID - primary key (numeric - autoincrement)

    I.e., when user enters a new inspection report, the Inspection ID is calculated (autoincrement). This is the table's primary key. User enters the location ID number, and date of the inspection. When user enters LastDtChecked field I want the field rule to fill in the last date checked for that location.

    I created an index on this table called 'findlast' that is LocationID + DateChecked. My field rule for the LastDtChecked field was previous("DateChecked","findlast"). The result is the DateChecked from last record entered in the table, not the last date checked for that location. What am I missing?

    Thanks, and I apologize for asking for so much help.
    Land of the Free, Because of the Brave
    Support our US Military

    #2
    RE: Another calculated lookup field rule problem

    I hope someone can help me...
    Land of the Free, Because of the Brave
    Support our US Military

    Comment


      #3
      RE: Another calculated lookup field rule problem

      JoAnn:

      You will need to use a filter that restricts your view of the file by the location ID.

      I hope this helps.

      bob adler

      Comment


        #4
        RE: Another calculated lookup field rule problem

        I am not sure how to go about doing that. I tried changing my index 'findlast' to just the locationID but I still get the value for the last record entered regardless of the location id.
        Land of the Free, Because of the Brave
        Support our US Military

        Comment


          #5
          RE: Another calculated lookup field rule problem

          Anyone have any ideas what I am doing wrong? Thanks.
          Land of the Free, Because of the Brave
          Support our US Military

          Comment


            #6
            RE: Another calculated lookup field rule problem

            JoAnn,

            I believe Robert has put his finger on your problem. If you select findlast as the active index of the primary table in your set and view the records in the default browse you will probably see that the previous record is the last-entered record in the table and Alpha5 is doing what you ask (which is not what you want).

            Instead of the previous function you need to use a lookup functions which takes a filter. As Robert says you will need to filter on the location code. (You state that location is a numeric field and I have a hunch that it should not be but that's another story.)

            If you post your application, or a sample somebody will be able to help you with the exact expression. If there is privacy issue you can either sanitize the data or send it to me personally.

            Bill
            Bill Hanigsberg

            Comment


              #7
              RE: Another calculated lookup field rule problem

              Thanks Bill. I will zip it up and post it here to be looked at. I worked on it all afternoon yesterday and was not able to get it to do exactly what I want. I was getting frustrated with it.

              Thanks again,

              JoAnn
              Land of the Free, Because of the Brave
              Support our US Military

              Comment

              Working...
              X