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

field rule to get previous value of a different field

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

    field rule to get previous value of a different field

    In field rules, is there a way to get the previous value of one field into a different field of the next record?

    What I am doing is entering timecard info where one job leads into the next, and it would be nice to take the ending time of the previous record and make it the default beginning time for the current entry. (See my example)

    PHP Code:
    Date     Job     Start   End   Total
    01
    /01    124     8am    10am   2 hrs
    01
    /01    134     10am   11am   1 hr
    01
    /01    144     11am   4pm    5 hrs 
    This is what I've tried so far,

    Code:
    dim lab_trans as p
    lab_trans = table.open("labor_transactions")
    lab_trans.fetch_eof()
    oldtime = lab_trans.End
    lab_trans.close()
    Begin.value_put(oldtime)
    but I don't know how to create field rule events very well, so I'm running into errors.
    Brad Steinfeldt

    #2
    Hi Brad,

    I would use the OnEnterRecord Event with the following:

    Code:
    '---------------------------------------------------------------------------------
    ' OnEnterRecord Event for labor_transactions table 4/17/06 CKL
    '---------------------------------------------------------------------------------
    
    'Populate Start field based on last entry in End field
    
    dim global oldtime as C
    t = table.current()
    t.fetch_last()
    oldtime = t.End
    t.start = var->oldtime
    Since I do not know the field types for start and end, you may need additional code if they are not character fields.

    Good luck
    Cheryl

    EDIT: Actually that code is probably not completely correct either. Since I am fetching the last record to get the End value, I am not sure if that will change the start value in the last record or the new record. You will have to test it and let us know what happens. If you get errors, let us know exactly what errors you are getting. Also let us know what the field type and widths are.
    Cheryl
    #1 Designs By Pagecrazy
    http://pagecrazy.com/

    Comment


      #3
      Originally posted by acceptthis
      In field rules, is there a way to get the previous value of one field into a different field of the next record?

      What I am doing is entering timecard info where one job leads into the next, and it would be nice to take the ending time of the previous record and make it the default beginning time for the current entry. (See my example)

      PHP Code:
      Date     Job     Start   End   Total
      01
      /01    124     8am    10am   2 hrs
      01
      /01    134     10am   11am   1 hr
      01
      /01    144     11am   4pm    5 hrs 
      This is what I've tried so far,

      Code:
      dim lab_trans as p
      lab_trans = table.open("labor_transactions")
      lab_trans.fetch_eof()
      oldtime = lab_trans.End
      lab_trans.close()
      Begin.value_put(oldtime)
      but I don't know how to create field rule events very well, so I'm running into errors.
      How about a button that placed the previous "end" in the "start" field when pressed?

      Button code

      start.value = previous("end")

      assuming that start is the object name of the start field on the form.
      There can be only one.

      Comment


        #4
        Thanks for your response and direction. Sorry for my slow response.

        I tried some variations of your suggestions, but I've realized I made it more difficult with the way I've set it up. The labor_transactions table is actually a child table and employees table is the parent of a set. This means, if I attach a script to the onEnter event, it only fires when I enter on the parent table, not the browse (labor_transactions table).
        It also means that the previous() function, suggested by Stan, doesn't work either. That's because the previous() function attempts to gather the previous data of the parent record.
        I'm re-thinking if I need the set or not. Maybe I don't.
        Brad Steinfeldt

        Comment


          #5
          To avoid all the coding you could do the following. Add a field to employee table, last_end_time. Use a post field rule to post the end time from labor_transactions to the new field in employee. Then have a "defaul value" field rule in labor_transaction that gets the value from employee.

          If you enter the field rule at the set level, Alpha makes it very easy for you - just pick the field from the other table.

          Now there are some details, like if you edit an older record to change a end_time value. If this can't happen (ha) then ignore the following. If this were to happen 1) the subsequent record needs to be edited also because its start time is no longer valid, and 2) editing the end_time field posts the revision to employee - which you do not want. My first inclination would be to use Time type fields in both tables and only post if the value in labor_transaction is greater that the value in employee. A Time type field includes both date and time.

          Bill.

          Comment


            #6
            thanks for your ideas!
            Brad Steinfeldt

            Comment


              #7
              previous_record()

              For any following this thread, the previous_record() function may work for most situations. See a description here:
              http://support.alphasoftware.com/alp...Help_Title.htm

              I'm still checking to see if it works for me.
              Brad Steinfeldt

              Comment

              Working...
              X