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

Default Date In Grid

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

    Default Date In Grid

    I have a GRID that has a date field from a table. When ENTERING a record into the grid how can I get the date field of the table to default to todays date? I have date() in the default portion of the field rules and the date is NOT being inserted. Where am I going wrong?

    #2
    Re: Default Date In Grid

    Hi Phil,

    The Field Rule Default has no effect on data-entry from a Grid; it won't fire your default value even after you press Submit. Calc Field Rules do work, so you might be able to issue an IF BLANK.... expression. You could also put this in the BeforeValidateNewRecords event:

    if DataSubmitted.MYDATE = null_value()
    DataSubmitted.MYDATE = date()
    end if

    But, on a Grid, none of that will make a value magically appear in a new record row before you press Submit, or have it pop in as you tab through the field.

    On a Dialog, the opposite is true, you can cause a default value to appear in any control.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Default Date In Grid

      How you doing? Long time no speak with the webinar. One of these days I will remember and not be to busy. Thanks for the Security Breach email.

      Your code did not work. I even tried changing it to isblank and even changed the code to eliminate the IF and just use the DataSubmitted.MYDATE = date() and the date still did not get placed in the table. I tried the code in all the Events and nothing is working. This should not be that difficult. I may have to resort back to a dialog where I have a bit more control.

      Comment


        #4
        Re: Default Date In Grid

        If it helps any, I use a similar feature to automatically insert the current date and time into my table upon the user clicking the submit button by using the following code in the "Before Validate New Records" section:

        function BeforeValidateNewRecords as v (DataSubmitted as P, Args as p, PageVariables as p)
        with PageVariables
        DataSubmitted.DateRecordEntered=date()
        DataSubmitted.TimeRecordentered=time()
        end with
        end function

        Seems to work fine for me.
        Sergeant Richard Hartnett
        Hyattsville City Police Department
        Maryland

        Comment


          #5
          Re: Default Date In Grid

          For the event to work, the field cannot be a Label. It could be a TextBox or Hidden (but not Hide Row) for example. For it to work the field has to be in the grid somewhere. And, I know you know this, MYDATE has to be your own field name. If you need the users to see the date, but not change it, and still have the default, create a Calculated field in the grid that shows data(). Use that as the visual, along with the real field as a Hidden.

          My example BeforeValidateNewRecords looks like this:

          Code:
          function BeforeValidateNewRecords as v (DataSubmitted as P, Args as p, PageVariables as p)
          with PageVariables
          if DataSubmitted.lastlogin = null_value()
          	DataSubmitted.lastlogin = date()
          end if
          end with
          end function
          Steve Wood
          See my profile on IADN

          Comment


            #6
            Re: Default Date In Grid

            As usual if I search long & hard enough I find an answer to my problem in a Steve Wood post; thanks.
            I now know why I can't get today's date to appear in a Detail View date field on an existing record when the field 'gets focus' (not a new record using the insert operation).

            It seemed that it should work. The user/operator, after tabbing into the field, can populate the field with the date picker by simply selecting the 'today' button in the picker. BUT they just want Today's date to appear for 99% of the time.
            It has been frustrating to not be able to simulate the same result for the user without them having to perform the extra keystrokes/mouse clicks. After all if the DatePicker has code to fill in the field object, why can't I figure out the code to do the same and include it in an instream java code.

            Also there is a need to have the date appear before they submit the update (they want the confidence of seeing the date before they save), ie., caninsert & canupdate work can help, but do not solve the user's request.

            Has anyone implemented this feature, ie., when tabbing into a date field on a Detail View, today's date appears (without using the date picker) before the user commits to save the updated record?

            Thank you,
            Otto Gustafson
            Last edited by otto17; 05-29-2013, 12:56 AM.

            Comment

            Working...
            X