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

creation date

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

    creation date

    Is there any function in A5V5 that will save an 'unchangeable' date?? In particular, the above 'record creation date'. Making the modify date work is simple..
    The only way that I can find is to acutally enter the date manually, but I would like an 'auto' function.

    D
    Tags: None
    #2
    RE: creation date

    This should be a Frequently Asked Question.

    Use field rules for the table.

    In Data Entry, establish a default field value of

    DATE()

    then, scroll down and set a SKIP expression of

    .T.

    When a new record begins the current system date will be entered by default, but the user can't change it then (or later) cause the field will always be skipped during data entry. User won't be able to put focus on the field to change it.

    --tom

    Comment

      #3
      RE: creation date

      Tom,

      That's a super idea! This forum is spectacular, but it would be great to have an FAQ section added where users could search for specific answers to common questions. Anyone at Alpha listening?

      --Michael

      Comment

        #4
        RE: creation date

        There already is an FAQ section.
        Bill Hanigsberg

        Comment

          #5
          RE: creation date

          Check the link in the top right quadrant of your screen.

          -- tom

          Comment

            #6
            RE: creation date

            There is also a tips section -- but no one has had any tips for quite some time.

            Russ

            Comment

              #7
              RE: creation date

              Tom,

              I did and IMHO it doesn't qualify, that is, it's an FAQ in name only. A real FAQ section would compile the most frequently asked questions on this forum, then put them in some sort of logical, searchable order. I find it hard to fathom that more folks ask about accented characters than a host of other issues such as [i]unchangeable dates[/u] and tabbed form issues.

              Just my 2 cents.
              --Michael

              Comment

                #8
                RE: creation date

                In alpha four, there is a script variable that contains an indicator that is that status of the current record. If the current record is in "enter" mode, then the variable contains the text "ENTER", if in change mode, then it contains "CHANGE". I've set a particular date field as a calculated field in an IF statement something like the following, which accomplishes what you're trying to do.

                if(%SYS_USER_MODE="ENTER",DATE(),DATE_FIELD)

                The current date will only be updated in the field if the current record is in ENTER mode, when the record is created. If you take an existing record and place it into change mode and the field updates, then it will be set to the value of itseld, the date that it was set to when the record was created, thereby keeping it the date it was originally set to.

                I don't know what in Alpha Five would accomplish this, but I'm sure the more advanced A5'ers can lead you in the right direction.

                Mike
                Thank you,
                Mike Konoff

                Comment

                  #9
                  RE: creation date

                  Frequently asked questions and correct answers will be gladly received by the Technical Documentation department here at Alpha Software.

                  Comment

                    #10
                    RE: creation date

                    Tom,
                    Would the field update to the current system date if the field rules were re-evaluated?

                    I have a table where I use the system date as the date of entry date - but never have to re-evaluate the field rules, so I'm curious.

                    Also, an update based on a range of records (by record number, or any other applicable field that could identify the recrods to have the same date) could be performed at the end of that data entry session.

                    Thanks,
                    Wanda

                    Comment

                      #11
                      RE: creation date

                      Wanda,

                      I shouldn't think so. Why don't you test it and let us know.

                      -- tom

                      Comment

                        #12
                        RE: creation date

                        Wanda,

                        Perhaps a word of explanation would help you understand my thinking. I would expect the date value to change if instead of using a default field value field rule with a field type 'user entered', one opted to make the field type 'calculated' and then used the Date() expression to compute the field value. This latter approach would recompute the field value for certain if you re-evaluated field rules.

                        -- tom

                        Comment

                          #13
                          RE: creation date

                          I stick my neck out and look what happens - I get an assignment from Tom!...LOL

                          Okay, I'll copy the table to a "test" table, just in case - 'cuz I need to keep the original data entry dates in tact.

                          Stay tuned...

                          Comment

                            #14
                            RE: creation date

                            Hey Tom,
                            First, re-evaluating a field rule using Date() as a default value does not change the date in the field :) Nice to know.

                            Nice to know how to force it to change, as well, if you wanted it to.

                            :)

                            Comment

                              #15
                              RE: creation date

                              Thanks, yes.

                              The second approach I mentioned (using a calc field rule instead of the default field value rule) is how folks track the date a record was LAST changed. It works well, with the one drawback that if for some reason the user decides to re-evaluate the field rules in all records the field value will be updated and it's meaning for the user lost. In this case the user needs to turn off the field rule before re-evaluating. --tom

                              Comment

                              Previous 1 2 template Next
                              Working...
                              X