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

xbasic SQL arguments problem

  • Filter
  • Time
  • Show
Clear All
new posts

  • xbasic SQL arguments problem

    I'm trying to send a datetime SQL field from one table to another (Both fields are datetime). Table one has 2014-03-18 09:10:14.760and when it goes over to the second table I get this: 2014-03-18 09:10:00.000. I need it to be exact.

    Here is the argument I wrote: args.set("arg9",e._currentRowDataNew.DateTimeCreated)

    I'm relatively inexperienced in xbasic but my understanding is that e._currentRowDataNew returns a character field but my fields are datetime. Could that be the issue? I thought about using convert_type in my argument but it looks like there is no datetime conversion ....only date (d) or time (t).

    Bottom line is I need the exact value from table one to go to table two.

    Table ones "DateTimeCreated" is populated by =now() ... perhaps there is a way to format this so it drops the seconds & milliseconds? ...then I wouldn't need to convert.

    Any help is appreciated.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Independent Developer & Consultant

  • #2
    Re: xbasic SQL arguments problem


    Convert type set as "T" returns a date/time value so
    should give you the full date time data. Always remember any data submitted in a UX or data on a row in a grid is in character format.


    • #3
      Re: xbasic SQL arguments problem

      Thanks Lance!
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Independent Developer & Consultant


      • #4
        Re: xbasic SQL arguments problem

        Here we are more than a YEAR later - this advice just fixed my issue! Thanks Lance, I knew I needed to do something with the DateTime fields to get them to update the other table correctly...
        NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"


        • #5
          Re: xbasic SQL arguments problem

          I am running into an odd thing and I am wondering if someone can help me.
          The field type for my field is simply TIME
          The field ("t_endtime") has a time picker, and the initial value is: =time("0h:0m am",now() )
          Display format: time("0h:0m am",<value>)

          The fields submit fine, however, I want to insert the value into another table so I am doing a typical xbasic function with an insert statement. There are a bunch of other fields and they are all inserting fine.
          The time field is giving me hell.
          even though I knew it was probably not right I tried several different convert_type statements and here are the results:

          if the xbasic statement is
          This yields 00:00:01 inserted

          if the xbasic statement is
          This yields NULL inserted

          if the xbasic statement is
          The xbasic insert fails

          I started writing this post and figured out the answer (after hours of thinking and testing) before I posted the question. Yep, the magic of the forum sometimes works before you post!
          I thought I would post ANYWAY for future reference to a new guy who may come across this and not know what to do. This forum has helped me so much over the years.

          So the issue is that the database field type is just "TIME" instead of "DATETIME" or "DATE" and it might be numbers but it aint exactly "Numeric" either.
          All of the above will not work, however this does:


          If you look here in the documentation:

          You will see the function CTOT which converts a char string to short time or TIME field type in MySQL meaning there aint no date part...

          I was going to just delete this post and not share my ineptitude but then I thought it might just save someone some time in learning and and if I had seen my own post earlier I would have know what to do without so much stupid trial and error.
          Of course, If I could have seen my own post earlier prior to making it I would be able to time travel, in which case I would just zoom ahead 10 yrs like DK does and just know stuff already.

          Cheers, all - hope this helps another!
          NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"