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

character to date field conversion

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

  • #16
    Re: character to date field conversion

    Yes, you are right....grrrr....newbie mistakes. I tried it and it all works fine, the dates are showing. Thank you so much for your patience and time ;)

    Comment


    • #17
      Re: character to date field conversion

      :) You're welcome
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


      • #18
        Re: character to date field conversion

        How does CTOD work when the existing table date field is populated 5/1//2010 and is character with many records. When I tried CTOD it converted the character date string to 5/1/2000. Also does the same when I use a new blank field formatted as date type, the same change of the date occurs. Any ideas ?

        Comment


        • #19
          Re: character to date field conversion

          CTOD("5/11/2010") converts to 05/01/2001, does anyone know why this character date strings is changed as a result of the conversion. This occurs on all records in the table which are different dates and CTOD returns the same changed date for all.

          thx lcg

          Comment


          • #20
            Re: character to date field conversion

            using build 2924_3560, I don't get the same results you're reporting.

            Code:
            ?ctod("5/11/2010")
            = {05/11/2010}
            
            ?ctod("05/11/2010")
            = {05/11/2010}
            Seems to be behaving correctly.

            Comment


            • #21
              Re: character to date field conversion

              Thanks for you information. However I have a table with character date. I tried the update table function not using the genie. I tried to convert the strings in the field using CTOD("start date")

              which yielded 5/1/2001 for each entry. Did you use the update method ? If not even when I create an empty filed to run the update the same thing happens. I will try again copying your comment.

              Thx
              LCG

              Comment


              • #22
                Re: character to date field conversion

                Lou, this is different from your first post. To unscramble this for you we will need to see sample data. You're not passing a literal character string to the function, you're passing a table field reference. We need a copy of the table to see what's actually being passed to the function.

                Comment


                • #23
                  Re: character to date field conversion

                  Tom,

                  when in the expression builder I do ctod("1/1/2010") which is the field content using F2. The result shown is 1/1/2008, when ok is done the error message "expression does not evaluate to a character value" is displayed.

                  What did you do to get a correct result ?

                  Thanks,

                  Lou

                  Comment


                  • #24
                    Re: character to date field conversion

                    I used the interactive window, not the expression builder.

                    Are we using the same build of vers 10?

                    Are you unwilling to furnish sample data?

                    Comment


                    • #25
                      Re: character to date field conversion

                      Tom,

                      Ok I am going to try and attach a copy of the table.

                      Lou

                      Comment


                      • #26
                        Re: character to date field conversion

                        I am on ver 9, also run 6 and 7 and would believe have 5 on my win 2000 laptop. Don't know where the file went, but it did. I just used the interactive window, copying the characterdate from one of thetables. The conversion yielded >
                        ?ctod("5 / 2 0 / 2 0 1 0")
                        = {05/02/2000}

                        Note the date converted to an unrelated date. It appears ctod cannot convert a true character date that was taken form a text file. I use Monarch to parse data from reports off the web which are either generic text or via a text program that works with Vista.
                        Last edited by lcgreene; 06-21-2010, 06:15 PM.

                        Comment


                        • #27
                          Re: character to date field conversion

                          Can you please try in the interactive window
                          ?? ctod(stritran("5 / 2 0 / 2 0 1 0"," ",""))
                          Most things are simple but unfortunately only after the first time

                          Comment


                          • #28
                            Re: character to date field conversion

                            Lou, the blank spaces in the character string you are passing to the function seem to be what's causing the issue. Blanks are characters, too. You're getting an invalid result because your input string of characters is invalid. It's the same as asking Alpha to turn the following into a valid date: ctod("5A/B2C0D/E2F0G1H0")

                            Strip the blanks from your input string, as Ton is suggesting.

                            Comment


                            • #29
                              Re: character to date field conversion

                              Tom,

                              Thanks, that is exactly as you said, the blanks spaces. Just never occurred to me.

                              Thanks, have a good one

                              Lou

                              Comment


                              • #30
                                Re: character to date field conversion

                                Good, and thanks to Ton for illustrating an easy way to clean up your data.

                                Comment

                                Working...
                                X