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

Short Time Field Problem

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

    Short Time Field Problem

    I am trying to update a short time field using update function in the operation area.

    I have the following scenario timeap is a character field with data in the format of 01:00 am

    The field I am updating is a short time field.

    using the code below I am able to test it on the expression builder and the resultant type is Y which is a short time type. Yet it gives me errors when I try to run it stating that the field and expression type must match.

    ctot(totime(toseconds(TIMEAP),11,0))

    can anyone tell me why. Is there a bug which I do not know of. I have updated with a current patch.

    #2
    Re: Short Time Field Problem

    SAY,
    I'm not sure but looking at the toseconds() function I believe you should be using either format 1, 2, or 12. Format 11 is not listed as one to be used. I am using version 8 so if there is a bug I could not verify one way or another.
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


      #3
      Re: Short Time Field Problem

      Hello MjkeC

      Thanks for replying. Let's see if I could simplify the problem.

      If I update the field with ctot("10p") it works like a dream. The result save in the field and I have no type error with the expression.

      It only happen if I put in a character type field in it. eg. ctot(starttime) where starttime is one of my database character field.

      Even though the expression result in a field type of Y as shown in the expression screen it gives that error.

      I have version 8 too maybe I should try in out in that version. Have you tried it out and does it work?

      Comment


        #4
        Re: Short Time Field Problem

        SAY,
        I can make it work by setting a character variable to equal your shorttime field's value and then using the variable in your expression. Try this in your interactive editor...changing table name, etc. to fit your database.

        Code:
         
        dim t as p
        dim vC_time as c
        t=table.open("your_table")
        vC_time=t.TIMEAP
         
        ctot(totime(toseconds(vC_time),11,0))
        
        t.close()
        EDIT: From my interactive Editor I get the following where sTime is a field in the transtest table.
        Code:
        dim t as p
        dim svC_time as c
        
        t=table.open("transtest")
        svC_time=t.sTime
        ctot(totime(toseconds(svC_time),11,0))
        t.close()
        
        ?toseconds(svC_time)
        = 84780
        ?totime(toseconds(svC_time),11,0)
        = "11:33 pm"
        ?ctot(totime(toseconds(svC_time),11,0))
        = 11:33:00 00 pm
        Last edited by MikeC; 06-11-2008, 09:08 PM. Reason: more info/example
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #5
          Re: Short Time Field Problem

          thanks Mike

          I guess we have to find ways to go around the problem sometimes.

          Josh

          Comment


            #6
            Re: Short Time Field Problem

            Josh,

            In this case I think it is more that the function toseconds() requires a character value...when I set the value of a character variable to equal the shorttime field value it became a character and so worked (I believe this is why...). Whenever you are creating an expression make sure you verify all the steps leading up to the entire expression to make sure it works. Which is how I found that it was toseconds() that was giving the error.

            But then again maybe a shorttime field should work in the function (seems logical), but as you said at least there was a way to go around the problem.
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment

            Working...
            X