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

Record the date time a record has been last edited

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

    Record the date time a record has been last edited

    I am using an access database backend. I want to record 'date' and 'time' when a record has been updated.

    I have tried
    1. CanInsertRecord event ... this works on new records but get upset when I try and update the field when I edit the record
    2. onAfterSQLCommandExecute Where I have some code run that updates the data after each time the record is updated...
    I could not get this to work!
    dim cn as sql::connection
    dim cs as c
    dim sql as c
    dim flag as l
    dim args as sql::arguments

    cs = e.cn
    flag=cn.Open(cs)
    sql = "UPDATE ProspectCompany Set LastChange = :nowarg WHERE " + e.primaryKeyWhereClause
    args.XML = e.argsXML
    args.add("nowarg",convert_type(now(),"D"))
    flag = cn.Execute(sql,args)

    3. The next possibility is to use Java to update the value of the 'LastChange' field when any other field is edited... Does anyone have code for that

    OR...... this seems to be usual for me in Alpha5.... I usually find there is a REALLY simple way to do things... i.e. a checkbox hidden somewhere!

    i.e. what is the simplest way to have a field that records the datetime of the last time the record was edited... that's all I'm trying to do..

    Thanks

    #2
    Re: Record the date time a record has been last edited

    I don't know if its possible with access but with MySQL you can simply have a field that is a time-stamp and set it to update automatically on any update from alpha or directly updating records.
    Chad Brown

    Comment


      #3
      Re: Record the date time a record has been last edited

      You can put the date and time into the record on the 'CanUpdateRecord' event you don't need to do any coding, se example.
      Snap9.jpg

      Comment


        #4
        Re: Record the date time a record has been last edited

        What I do is append three fields to all my tables and allow MySQL to update the fields via a series of triggers and procedures. Attached is the SQL for the 'tbl', tiggers and procedure creation.

        CREATE TABLE tbl (
        ID int AUTO_INCREMENT NOT NULL,
        .
        .,
        Date_Created datetime,
        Date_Edited datetime,
        Date_Deleted datetime,
        /* Keys */
        PRIMARY KEY (ID)
        ) ENGINE = InnoDB
        CHARACTER SET ascii COLLATE ascii_bin;

        ALTER TABLE tbl
        AUTO_INCREMENT = 1000000;

        CREATE TRIGGER tbltInsert
        BEFORE INSERT
        ON tbl
        FOR EACH ROW
        BEGIN
        /* Trigger text */
        SET NEW.Date_Created = CURRENT_TIMESTAMP();
        SET NEW.Date_Edited = CURRENT_TIMESTAMP();
        END;

        CREATE TRIGGER tblUpdate
        BEFORE UPDATE
        ON tbl
        FOR EACH ROW
        BEGIN
        /* Trigger text */
        SET NEW.Date_Edited = CURRENT_TIMESTAMP();
        END;

        CREATE PROCEDURE tblDelete
        (
        IN ID int
        )
        BEGIN
        /* Procedure text */
        UPDATE
        tbl
        SET
        Date_Deleted = CURRENT_TIMESTAMP()
        WHERE
        tbl.ID = ID;
        COMMIT;
        END;

        CREATE PROCEDURE tblUndelete
        (
        IN ID int
        )
        BEGIN
        /* Procedure text */
        UPDATE
        tbl
        SET
        Date_Deleted = NULL
        WHERE
        tbl.ID = ID;
        COMMIT;
        END;

        CREATE PROCEDURE tblZap ()
        BEGIN
        /* Procedure text */
        DELETE
        FROM
        tbl
        WHERE
        tbl.Date_Deleted IS NOT NULL;
        COMMIT;
        END;
        When the record is created 'inserted' the 'tblInsert' trigger sets the Date_Created and Date_Edited fields, and when the record is 'updated' the 'tblUpdate' trigger sets the Date_Edited field. The 'tblDelete' procedure I call when the user deletes the record and this sets the Date_Deleted field. The record is not really deleted but the filter on my grid filters records on Date_Deleted = NULL for users allowing administrators to undelete the record using the 'tblUndelete' procedure. I run the 'tblZap' procedure once a month to delete those records permanently.
        The advantage of using JimDK�s approach is that you can get the username field updated as well. I have also noticed that when uploading an image, using Image Upload feature pack, it does not fire the �tblUpdate� trigger. I find this very odd.
        I hope this helps.
        George Frankland
        "A man is but a product of his thoughts - Think you are, and you will be."

        Comment

        Working...
        X