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

Default date value

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

    Default date value

    I have a simple set with one parent and one one to many child table. In the child table I enter dates etc. If my last entered date was e.g. 02.May 2007 how can I get for next entering child record in embedded browse on the form defaulted date 03.May (so last date + 1). In field rules there is the "previous value", but I need "previous +1". I tried also with "lookup..", with "last..", but cannot manage to work. The "date()" defaults me only today's date, but I need defaulted the first date after my last entered.

    Tks
    Ales
    Tags: None
    #2
    Re: Default date value

    Originally posted by Ales View Post
    I have a simple set with one parent and one one to many child table. In the child table I enter dates etc. If my last entered date was e.g. 02.May 2007 how can I get for next entering child record in embedded browse on the form defaulted date 03.May (so last date + 1). In field rules there is the "previous value", but I need "previous +1". I tried also with "lookup..", with "last..", but cannot manage to work. The "date()" defaults me only today's date, but I need defaulted the first date after my last entered.

    Tks
    Ales
    Use "Simple default expression" instead of Previous Value.

    Expression

    previous("yourdatefieldname")+1

    The previous() function requires the quotes so you would replace the portion in red with your field name.
    There can be only one.

    Comment

      #3
      Re: Default date value

      Ales,
      Try this as the default value in the field rules for your date field:

      previous("your_date_field")+1

      The user should still be able to type over the date if needed. The previous() function is supposed to return a type A (any value), but the field name must be in quotes.
      Robin

      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

      Comment

        #4
        Re: Default date value

        Stan you type fast!
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment

          #5
          Re: Default date value

          Originally posted by MoGrace View Post
          Stan you type fast!
          And in color!
          There can be only one.

          Comment

            #6
            Re: Default date value

            Tks Stan and Robin. If I try to enter the "previous" in the filed rules for the set and I manually enter the date filed name, it gives an error message "Expression does not evaluate to a date value". If I enter the "previous" directly into the child dbf field rules it accepts it. But my concern is the warning sentence in the help file for "previous" function:
            "If you are working with a set, PREVIOUS() returns field values only from the previous record in the primary table."
            If the rule entered in child dbf level and later edited in set level, it fires again the a/m error message.
            But presently it works, only I don't know how it will behave in any situation because of the warning in the hep file as explained above.

            Ales

            Comment

              #7
              Re: Default date value

              Ales,

              So, is your requirement:

              a) one more than the last child table record that was entered (as you originally said); or

              b) one more than the last child table record entered for the current parent and something else if there are no child table records for the current parent?

              Comment

                #8
                Re: Default date value

                Tom,

                b) one more than the last child table record entered for the current parent


                Tks
                Ales

                Comment

                  #9
                  Re: Default date value

                  ... and if there is no previous child table record for the current parent?

                  Comment

                    #10
                    Re: Default date value

                    Tom, in such case today's date can be defaulted.

                    Ales

                    Comment

                      #11
                      Re: Default date value

                      Ok, if nothing else works I think you could build a function that would use dbmax() to find the highest (latest) date value for a given link field value, and then return one more than that, or the current system date. This function could then be called in field rules, passing the current link field value to the function as an argument.

                      Comment

                        #12
                        Re: Default date value

                        Here's another idea using a global variable because previous() is going to get the last child date entered even when a new parent is entered.

                        Let the parent record set the date initially whether a date is used in the parent record or not - you can use the OnSaveRecord event in field rules to set a global variable to the initial value you want, eg. date(). Then put this variable as the default value for the child record. In the child OnSaveRecord event, increment the global variable by 1. When another new parent is entered the global variable is returned to the date set by the parent and defaults to that date with the 1st child entered and is incremented for each child you add.

                        You might have to fiddle with record deletes however - I didn't test that yet. If you have a date field for the parent record you could add an OnArrive script to return the variable back to that value if the user clicks on that field.
                        Robin

                        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                        Comment

                        Previous template Next
                        Working...
                        X