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



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

Date textbox format mismatch with SQL Server in Dialog2

  • Filter
  • Time
  • Show
Clear All
new posts

    Date textbox format mismatch with SQL Server in Dialog2

    I use a dialog to add/edit records, instead of the detail view, in a grid.
    Everywhere needed, in the grid and/or the dialog, i have set date format as dd/mm/yyyy.
    Whenever i want to edit a date field, i select DateOnlyFormat in the calendar properties.

    When adding a new record, the date is displayed ok. In the grid, the date field is displayed ok as well.
    When editing that same record, the date appears as mm/dd/yyyy hh:mm (american date format).
    I am sorry i cannot attach screenshots, am currently on holidays quite far (Thailand), but i will need this when i get back next week :-)

    Can anyone help with a workaround?


    Re: Date textbox format mismatch with SQL Server in Dialog2

    Correct me if I have this wrong, but SQL (SQL Server, or MySQL) deal with dates in a yyyy-mm-dd format.
    In my dialog, if I use the <Default> or <DefaultDateOnlyFormat> the date displayed will be dd/mm/yyyy which is good but, as you say, when you edit that date the month and day are switched.
    I put in a custom format, choosing from the list, of dd/MM/yyyy and this solves the issue for me.

    I did find another problem, however. Using the <Default> format for Date, when I retrieve a record the Date is formated as dd/mm/yyyy. When I click on the date picker a different date is displayed than the record.
    E.g. my displayed date is 29/08/1995 and the date picker displays May 8, 1995. When I choose a custom format all is fine.


      Re: Date textbox format mismatch with SQL Server in Dialog2

      Hi David
      Tried to use custom format as you suggested, but *the problem still persists*...i also tried putting time("dd/MM/yyyy",<value>) in the Display Format property under "Textbox properties" but that doesn't help as well.
      I also noticed that the calendar pops up at the wrong date ( either with the defaultdateonly or custom format as per your suggestion ), but i guess this is related to the fact the date isn't formatted as expected and that confuses the calendar.


        Re: Date textbox format mismatch with SQL Server in Dialog2

        Here are the pics:
        first one is taken in working preview, or when adding a new record: datebugwp.JPG
        second one is at runtime, i select a record where the dates are January 18, 2012, but look the way it is displayed datebugedit.JPG
        Notice in the second pic, that the calendar displays a completely wrong date, and also you cannot see the rest of the date (since i've restricted the width to the date part only), but in fact if i scroll i see 01/18/2012 00:00:00 AM ...
        Bummer :-(


          Re: Date textbox format mismatch with SQL Server in Dialog2



            Re: Date textbox format mismatch with SQL Server in Dialog2

            In my Dialog I have a button which populates the data, in this case a date field, with data from a MySQL table. I enter a key into a field on the dialog and hit the populate button and my date is read from the table.

            Just using defaults for the date field, the dates are all messed up. The display in the field is 22/12/2011. When I click on the calendar of the date field the displayed date in the calendar is October 12, 2011.

            Then I get into the Textbox Properties of the date field and selected a display format of dd/MM/yyyy and this turns into time("dd/MM/yyyy",<value>). I run the dialog and the displayed date in the calendar is October 12, 2011. Then I get into the Date/Time Picker Properties of the date field... the Date format have a default setting of <Default>. I change this by selecting Custom and choosing a Date Portion of dd/MM/yyyy - I leave the Time Portion blank and the Date Format now reads dd/MM/yyyy.

            Now when the dialog is run, I populate the dialog, the displayed date is 22/12/2011 and the pop-up calendar reads December 22, 2011... so it looks like all is ok.


              Re: Date textbox format mismatch with SQL Server in Dialog2

              Hi David
              Will start from scratch and do step by step as per your post, will get back to you with findings

              Thank you for your patience


                Re: Date textbox format mismatch with SQL Server in Dialog2

                Still doesn't work!!@#!
                I already had all the settings exactly as per yours. When adding a new record, all is great. When editing an existing record, i have a 'semi-wrong' behavior in Working Preview - i.e the date shows in the correct dd/mm/yyyy format, but it also adds the time portion. I worked around this by setting the width of the control to only the date part.
                When running in the browser though, it's completely wrong, date shows mm/dd/yyyy ( also showing the time part ) and also when clicking on the calendar it shows a bad date.
                I think i am going to file a bug report.


                  Re: Date textbox format mismatch with SQL Server in Dialog2

                  I get correct behaviour both Working and Published.

                  What about the date format setting for the server and/or your client PC?