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

Custom Date Format

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

    #16
    Re: Custom Date Format

    Tom, I have a similar issue as Bruce had in that I would like to have my date stored as YYYY-MM-DD in the date field (date_rev).

    On my form, I have an object button (not sure how I stumbled across this) that inputs the current date into the date field.
    Using the " -events -on push" , feature for this object button and this code, the format gets changed on the form to what I want

    Date_String = date_format(DATE() , "yyyy-MM-dd")
    parentform: date_rev.value = date_string

    When I look at the date_rev field of the table, it is stored as MM/DD/YYYY. If you put your cursor in the field on the form, it will revert to mm/dd/yyyy.

    The issue I am having with this is that I want to automatically attach this date to a file name that is generated from some of the fields on the form layout when I save the report as a pdf file.

    I have been able to overcome this by creating a 10 character field (date_rev2) and then adding this code

    parentform: date_rev2.value = date_string

    to the same object button that formats the current date as YYYY-MM-DD.

    I prefer the YYYY-MMM-DD format as this sorts better when you use explorer to view the saved reports and the /// can not be used in a file name.

    I was wondering if I was overlooking some way to do this in the A5 setup without having to add the extra field and code as you mentioned the dates were stored as yyy/mm/dd

    Larry Ternowski

    Comment


      #17
      Re: Custom Date Format

      The issue I am having with this is that I want to automatically attach this date to a file name that is generated from some of the fields on the form layout when I save the report as a pdf file.
      Code:
      report.saveas("your report name", "PDF", "your_filter_expression", "your_order_expression", "C:\test"+_date_format(DATE() , "yyyy-MM-dd")+".pdf", .T.)
      There can be only one.

      Comment


        #18
        Re: Custom Date Format

        Stan, I think I'm squealing and I'm not annoyed.

        Need to try this but I think what you are showing me is that this save will be to the current date and does not require a date field.
        If so, this will require a thinking realignment and has huge potential for many other report saves

        Thanks

        Larry

        Comment


          #19
          Re: Custom Date Format

          Yep. You can build the save as file name from as many pieces as you want.

          alltrim(path_field)+chr(92)+alltrim(customer_name_field)+_date_format(DATE() , "yyyy-MM-dd")+".pdf

          just to name one possibility.

          Does help to remember that certain characters are still illegal in file names.
          Last edited by Stan Mathews; 12-27-2013, 07:43 PM.
          There can be only one.

          Comment


            #20
            Re: Custom Date Format

            My reply should have read....

            Code:
            report.saveas("your report name", "PDF", "your_filter_expression", "your_order_expression", "C:\test_"+date_format(DATE() , "yyyy-MM-dd")+".pdf", .T.)
            There can be only one.

            Comment


              #21
              Re: Custom Date Format

              The humble CDATE() returns a chronological string YYYYMMDD, can be used for placing in filenames or fields and include in a sort.

              Comment

              Working...
              X