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

Updating of a date field

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

  • Updating of a date field

    I am a novice programmer in A5V9. I am trying to set up a date field that will automatically update itself once a record is "modified" not just viewed. Can anyone tell me how to set up a field rule (or script)so that this happens?:confused:

  • #2
    Re: Updating of a date field

    i have a date field which i made calculated in the tables field rules with Date() as the calculated field expression.

    whenever any field in that record is amended the date changes to todays date.

    Comment


    • #3
      Re: Updating of a date field

      Originally posted by richard2007 View Post
      i have a date field which i made calculated in the tables field rules with Date() as the calculated field expression.

      whenever any field in that record is amended the date changes to todays date.
      NO! NO! NO! Do NOT do this.

      It is a very common mistake made by almost everyone. It works most of the time but then someone does something like a global update and all of a sudden EVERY record in the table shows today's date! (There are other actions that have the same issue but I don't recall what they are since I haven't used a calc field for this in many years.)

      Make your "last modified" field (mine is named change_dtf) a simple user entered field then add this in the CanSave event of the table (note that this is the CanSave event of the table - not the OnSave event and not the event in the layout):
      tc = table.current()
      tc.change_dtf = date()
      Of course, you should change the "change_dtf" to be your own field name.

      I can't tell you how many times someone has done this (used a calc field) then ended up calling me or posting on the message board to find out how to fix the problem - and maybe recover the original dates. There is no recovery unless you have a backup that can be restored. Of course, that also undoes the global update (or other action).

      This method also provides some other possibilities. For example, there are many cases where I want the change date to indicate that a USER changed the record and I don't want it to change as the result of some xbasic/Action Script action. For example, I might change the "last printed" date in an invoice record via xbasic after running a print operation. This isn't a user change so I really don't want to update my change_dtf field. If change_dtf is a calc field, it WILL change when the print date is updated.

      There is one minor downside to this method. If you edit a record with xbasic/Action Script, the routine must include the change to the change_dtf field since the CanSave table event doesn't fire when editing with xbasic.

      Disclaimer: I haven't checked the new action that forces a5 to run field rules from xbasic. This may solve the problem. Of course, it may also cause other problems, like the issue I related above with adding a print date, so you'll have to test that one for your particular situation.
      Last edited by CALocklin; 01-15-2010, 05:12 PM.

      Comment


      • #4
        Re: Updating of a date field

        think i will change my app.

        Comment


        • #5
          Re: Updating of a date field

          I'd also like to point out that to use Cal's way if you want to ALWAYS have that table's field changed for ANY form/browse that uses it and also for all fields that can be modified.

          There are times that I have fields on a form that change but do NOT want the modified date to change unless certain fields data changes....then maybe the OnChange event of the form(s) fields would be a better choice--more work but adds the aforementioned flexibility of not having the modified date field updated in certain cases.

          As always, there are many ways to do things and each have their merits and such.
          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


          • #6
            Re: Updating of a date field

            Thanks all...I will see how competent I am and see if I can implement your suggestions...

            Comment


            • #7
              Re: Updating of a date field

              Good point.

              And, if it's not form specific but you did/didn't want to update the field for certain changes, you could compare the field values in the CanSave event to what they were before the record was changed. There are at least two ways to do that:

              The old way - include an OnChange record event in the table that sets a Shared variable to the original value of the fields to be tested.

              Another old way - <fld>.Initial_value_get() might work but it's a pain to use because you first have to get a field pointer and I'm not sure if it will work in this situation.

              The new way - I know there's a newer function for getting the original field value before a table is saved but I don't remember the name of that function and can't find it in the Help file (it's probably not there since it's a newer function). I also can't very well look it up in What's New, etc. since I don't already know the name. If someone can tell us the name, I'll add it to my A5v5_Xbasic_Help file which has much friendlier keyword searches so I can find it in the future. ("A5v5" is just the name - it also has many v6 functions and some v7,8,9 functions and it's free)

              Comment

              Working...
              X