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

Date when record was changed?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Date when record was changed?

    Hi A5 Members:

    I have an application for customer records! On the table I have a date field call "dated_changed"! I want the date in this field on a form change to the current date each time the record is edited or changed "only when a change is made"! Can it be done! Have tried different ways but can't get this to happen! I would appreciate anyone's suggestions!
    Tags: None
    #2
    RE: Date when record was changed?

    Bob, it depends on what you mean by "only when a change is made".

    Of course, A5 will register ANY change - even speling corecshuns. If you want to change the date in this case, you can simply define the Date_Changed field as a calculated field where the calculation is: date()

    The problem comes when you only want to indicate a changed date for REAL data changes and not just simple things like a spelling correction. In this case, it could only be done through user intervention. (OK, this may sound like a silly comment to people on this board but one customer did ask me about this.)

    Cal

    Comment

      #3
      RE: Date when record was changed?

      Hi Bob
      Go to Field rules, make the Date Change field a calculated field and then in the expression area type: date()

      That should do it!

      Dan
      Dan

      Dan Blank builds Databases
      Skype: danblank

      Comment

        #4
        RE: Date when record was changed?

        Thanks Cal and Dan!

        Dan your suggestion worked just fine for what I was wanting1 The date to change anytime the record was change, spelling or corrections or additions!

        Thanks for the speedy responce, I have come to expect that though from the A5 message board and it's uses and I should be suprized!

        Comment

          #5
          RE: Date when record was changed?

          Just remember that this method will post the new date every time the record is opened and saved, whether changes are made or not, as well as during any table-wide update - which will reset all records to the same date.

          Finian
          Finian

          Comment

            #6
            RE: Date when record was changed?

            to add to finian, if you have any summary fields in that table and the ammount changes it will change the date. The way I have done this is have a variable string set with, all the fields that are revelent to when you would want to change the date, in the on can change record event and then on the on save record event match it to the current record and if it changed then change the date feild.

            good luck

            Comment

              #7
              RE: Date when record was changed?

              you could make it a calculated field, but test what mode the db is in. if not change or enter, leave it alone. if it is a user change ort enter mode, then update. We use this method all the time.

              Comment

                #8
                RE: Date when record was changed?

                As an addition to this thread I'd like to mention that I also add a 'created date' to my dbf records as well as a last change date.

                I've found it useful at times when researching problems.

                Comment

                  #9
                  RE: Date when record was changed?

                  In applications where an audit trail is needed, I have a table called audit.dbf. Any tables in the app which need an audit trail are specified in another table called auditsetup.dbf. When a record is edited, the following information is written to audit.dbf:

                  1. table name
                  2. record I/D - this is the value of a unique identifier for the record being changed , e.g. an auto-incremented I/D field - NOT the record number, which may change.
                  3. field name
                  4. old value
                  5. new value
                  6. date
                  7. time
                  8. user name

                  Similar information is written to the audit table when a new record is entered, or a record is deleted. The system is based on the article by Peter Wayne in Alpha forum (Nov 97).

                  Tony

                  Comment

                    #10
                    RE: Date when record was changed?

                    hi bob
                    check this out

                    Msg ID: 33931
                    Subject: RE: Time tracking when a record is changed
                    Author: John Zaleski
                    Date: 01-23-2001 00:51
                    File:

                    One thing to note if you make it a calculated field: If you do any kind of global update or script that changes another value on that record, let's say bill or pay rate, the calc time field will be changed also. If you think this could be a problem try the following:

                    Create a global variable with the table "timenow"
                    Oninit event of form set timenow to "auto"
                    Onexit event of form set timenow to " "

                    Calculated field "timestamp" field rule:
                    IF(var->timenow = "auto",time(),timestamp)

                    This should only do the time stamp when in that form. I have time keeping programs where the bill or pay rate had to be handled with a global script, but I wanted to keep the timestamp on the record.

                    Daniel Weiss
                    Daniel Weiss
                    EZ Link Software

                    Comment

                    Previous template Next
                    Working...
                    X