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

variable to date

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

    variable to date

    I have a variable that contains the month ie "January" and another vbl that contains the year ie "2002". How can I convert this to a date value such as 01/01/2002? Sort of the reverse of CMONTH. (I can do this in the expression builder with a long if statement but there must be a better way) Thanks in advance.


    Russ

    #2
    RE: variable to date

    Russ,

    Looks like something that could be created as a global UDF and contributed to the Code Archive!

    DMONTH("January") could return "01"

    DMONTH("February") could return "02"

    and so on


    It could be extended to cover

    DMONTH("Feb") could return "02"

    DMONTH("Jul") could return "07"

    etc.

    When you design the function you might want to force the argument to upper case before processing it within the function. That way you'd be covering all possible capitalization sequences.

    -- tom

    Comment


      #3
      RE: variable to date

      Any takers?
      I hope someone beats me to it.

      I'll look at this tonight. I guess in a UDF a case or select would work OK.

      Russ

      Comment


        #4
        RE: variable to date

        I'll put this in the code archive, too:

        ' -------------------------------------------------------
        ' by Steve Workings - February 12, 2003
        ' Converts Month name or standard month abbreviation to
        ' 2-character number
        '
        ' Sample usage:
        ' ?DMONTH("Jan")
        ' = "12"
        ' -------------------------------------------------------
        FUNCTION DMonth AS C (MonthName AS C )
        select
        case "Jan" $ MonthName
        DMonth = "01"
        case "Feb" $ MonthName
        DMonth = "02"
        case "Mar" $ MonthName
        DMonth = "03"
        case "Apr" $ MonthName
        DMonth = "04"
        case "May" $ MonthName
        DMonth = "05"
        case "Jun" $ MonthName
        DMonth = "06"
        case "Jul" $ MonthName
        DMonth = "07"
        case "Aug" $ MonthName
        DMonth = "08"
        case "Sep" $ MonthName
        DMonth = "09"
        case "Oct" $ MonthName
        DMonth = "10"
        case "Nov" $ MonthName
        DMonth = "11"
        case "Dec" $ MonthName
        DMonth = "12"
        end select
        END FUNCTION
        -Steve
        sigpic

        Comment


          #5
          RE: variable to date

          Jeez, you're fast!
          Thanks, I did it temporarily as a calc fld using case but will convert to this.

          Russ

          Comment


            #6
            RE: variable to date

            Steve,

            might I suggest a small change to avoid capitalization issues with the input value:

            Instead of:

            case "Jan" $ MonthName
            DMonth = "01"
            case "Feb" $ MonthName
            DMonth = "02"

            how about:

            case "JAN" $ Upper(MonthName )
            DMonth = "01"
            case "FEB" $ UPPER(MonthName )
            DMonth = "02"

            and so on ?


            -- tom

            Comment


              #7
              RE: variable to date

              I thought about it as I did it. Your suggestion is one of several improvements that could be made. But, for this specific one, upper/lower case shouldn't be an issue.

              - Steve
              -Steve
              sigpic

              Comment


                #8
                RE: variable to date

                I agree with Steve that case should not be an issue in this example. See the code below from an interactive window:

                ?"Dec" = "DEC"
                = .T.
                ?"Dec" == "DEC"
                = .F.

                That said, in many instances it is a good idea to force upper to eliminate any case-related issues. But instead of the code Tom has offered, it would be more efficient to simply add a the following as the first line and then leave the rest as Steve has provided.

                MonthName = Upper(MonthName)

                Done this way, the Upper() is always only run once, compared to as many as 12 times (for December) in Tom's example. Upper() is pretty fast so your users may not notice the performance difference - I just wanted to point this out though for future reference when you may be doing something more complex than Upper().

                -Lenny

                Lenny Forziati
                Vice President, Internet Products and Technical Services
                Alpha Software Corporation

                Comment

                Working...
                X