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

Initial value for date w/ clientSideDateFormat

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

    Initial value for date w/ clientSideDateFormat

    I'm implementing a site that uses session.__protected__clientSideDateFormat to provide the correct date format (duh).

    But the implementation doesn't seem to affect an initial value.

    So, with the initial value set to =date()

    the value sitting there for a new record is 05/01/2011

    even if the clientSideDateFormat is set to dd/MM/yyyy where it does properly affect all fields with a committed date.

    I can make my own UDF to manage this, but I'm wondering if the grid's controls should be doing it or I'm missing something.
    -Steve
    sigpic

    #2
    Re: Initial value for date w/ clientSideDateFormat

    Steve,

    Not sure I understand your post completely, but I am having an issue that may be similar. I am attempting to populate initial value of a date field with the value stored in a session variable. If I hard code a string into the initial value field, it will populate correctly, but when I set it equal to a session variable it will not populate. This is only an issue for date fields and not for any other types.

    Any thoughts?

    Comment


      #3
      Re: Initial value for date w/ clientSideDateFormat

      IME, the client side date format doesn't change anything... It all depends on the format on your grid properties->Date Format

      Should this be a bug ?

      Comment


        #4
        Re: Initial value for date w/ clientSideDateFormat

        I'm well through figuring this out now, so I'm happy to discuss. Basically:

        A date or calendar selector will do the job just fine in matching the session.__protected__clientSideDateFormat.

        But, if you try to supply a date -- such as through the insert of a session variable -- to a control where your variable format is different than you want in the control, you won't get what you want. In other words, you can't expect the control to re-format your date for you when you're inserting an "incorrectly" formatted value.

        The solution, of course, is to format the date value the way you need it before trying to insert it. One handy function is the dtoc() function and it's formatting options, e.g.

        dtoc(date(),"2/")
        -Steve
        sigpic

        Comment


          #5
          Re: Initial value for date w/ clientSideDateFormat

          Cant get it to work. I have an AffFileDate field whose initial value is set to "=session.affdate" and whose display format is "time("MM/dd/yyyy",<value>)"

          I also have a for on the same page as the grid it calls the page and uses page variables to populate the session variable in the following manner.
          Code:
          if eval_valid("cmd") 'If for submit button was pressed
          	session.xfilpre = xfilpre
          	session.affdate = dtoc(ctod(affdate),"1/") 'convert to date then to string to ensure correct format
          else
          	session.affdate = dtoc(date(),"1/") 'hard coded just to see if I can get it to work
          end if
          still will not populate the field correctly.

          Comment


            #6
            Re: Initial value for date w/ clientSideDateFormat

            Hi All,

            If anyone stumbles across this old thread looking for a solution this video from Selwyn might help

            http://screencast.com/t/EOU4y3tFhXU

            Cheers
            Peter

            Comment

            Working...
            X