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

How to make the current date the default value in a Dialog Component?

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

  • How to make the current date the default value in a Dialog Component?

    How do i set the current date to be the default value in a dialog Component? Numbers and strings are easy to set but for the current date which is Date() is not recognized in a Dialog component.

  • #2
    Re: How to make the current date the default value in a Dialog Component?

    How are you doing at the moment?

    Set the default value to =date()
    Last edited by Keith Hubert; 04-23-2012, 07:48 AM.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


    • #3
      Re: How to make the current date the default value in a Dialog Component?

      Setting Your Date field = Date() does not work in a dialog component. That date will not be saved in the table when the dialog is submitted. This behavior may have been changed in the latest release.

      In the afterDiaogValidate event, you normally define an action script to save data to the table

      e.g.,

      ExecuteServerSideAction("Save Data::Save Data")

      JUST BEFORE this action you can put YOUR FIELD NAME - e.g., OrderDate. Clip this code and enter it exactly with no additional spaces anywhere in any of the lines. You may have to add other fields such as calculated fields that depend on other calculated fields in this code segment. Just put the field name below OrderDate and put it flush left if they are not being saved.

      if e.dirtyColumns <> ""
      dim AddFields as c
      Addfields = <<%text%
      OrderDate
      %text%
      e.dirtyColumns = remove_blank_lines(e.dirtyColumns + crlf()+ AddFields)
      end if

      Note: When I submit this, all the lines are flush left. I have lines 2,3 and 6 indented on the pre-submit. Do not indent any other lines or the code will not work.
      Last edited by Chet Sapino; 04-23-2012, 11:18 AM.
      Regards,
      Chet Sapino
      President,
      SAPINO Enterprises
      6451 Pheasant Rd
      East Syracuse, NY 13057

      Comment


      • #4
        Re: How to make the current date the default value in a Dialog Component?

        Setting =date() works for me on a dialog. I have a Textbox type=Date with a default value of '=date()'. It correctly sets the date to today's date and it saves when the form is submitted.

        Comment


        • #5
          Re: How to make the current date the default value in a Dialog Component?

          What happens if you change the default date? Does it save the modified date? I reported a problem with this default stuff awhile back and they said it was going to be changed in the future.
          Regards,
          Chet Sapino
          President,
          SAPINO Enterprises
          6451 Pheasant Rd
          East Syracuse, NY 13057

          Comment


          • #6
            Re: How to make the current date the default value in a Dialog Component?

            I figured it out based on the previous help by Jim Coltz. Make a Javascript function:

            function today(){
            var a = new Date();
            a.setDate(a.getDate())
            return a.getMonth()+1 +"/"+a.getDate()+"/"+a.getFullYear()
            }

            then call it in the calculated property of the field. (dialog component)

            Comment


            • #7
              Re: How to make the current date the default value in a Dialog Component?

              That's doing it the hard way. Just use my code above for any field.
              Regards,
              Chet Sapino
              President,
              SAPINO Enterprises
              6451 Pheasant Rd
              East Syracuse, NY 13057

              Comment


              • #8
                Re: How to make the current date the default value in a Dialog Component?

                Chet,

                I'm a bit lost with your code. It looks to me that your code is going to create a new field each time the record is saved. I'm sure that is not what you intended, is it?

                It seems that Jetson is now in the swing of things and is getting to grips with the way things can be done with Alpha. Well done Jetson!
                Regards
                Keith Hubert
                Alpha Guild Member
                London.
                KHDB Management Systems
                Skype = keith.hubert


                For your day-to-day Needs, you Need an Alpha Database!

                Comment


                • #9
                  Re: How to make the current date the default value in a Dialog Component?

                  I got this code directly from Alpha - Jerry Brightbill and it works. I reported difficulties in saving default values for fields. If you play around with the dialog component and use a number of calculated fields and default fields that can be changed by the end user, you may find the data in some of these fields is not being saved. I found this out with a default date field that could be changed by the end user. I contacted Alpha about it and Jerry sent me this code.

                  Thus, you add these fields to e.dirtycolumns - you purposely make them dirty - and they get saved.

                  This is a very simple solution. all you need to do is add a column that is not being saved in that code because it somehow isn't dirty.

                  With my dialog I am working on, I had to do the following with several fields. Most of these are calculated fields that were not being saved to the SQL table after updating other fields in the dialog that these depend on.


                  if e.dirtyColumns <> ""
                  dim AddFields as c
                  Addfields = <<%text%
                  OrderDate
                  OrderQuote
                  Subtotal
                  ExtAmount
                  SalesTax
                  OrderTotal
                  Balance
                  DiscAmount
                  TotalProfit
                  %text%
                  e.dirtyColumns = remove_blank_lines(e.dirtyColumns + crlf()+ AddFields)
                  end if
                  Regards,
                  Chet Sapino
                  President,
                  SAPINO Enterprises
                  6451 Pheasant Rd
                  East Syracuse, NY 13057

                  Comment

                  Working...
                  X