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

Storing a Time Variable

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

    Storing a Time Variable

    Although I've purchased V10 and now V11, I'm still working in a V9 application that didn't play well under V10.

    Out of some fit of craziness, realizing that I was a number of versions back in V9, this morning I updated to the last release version and started having problems with the first thing I tried.

    I have a short script that simply stores a global Time Variable from a Date/Time field in an Alpha Table.

    Code:
    dim tbl as p     
    tbl = table.open("V2T_Msgs")
    dim recno as n 
    recno = -1
    'select record number order
    tbl.index_primary_put("") 
    'go to last record in table
    tbl.fetch_last()
    dim last_record as n 
    last_record = tbl.recno()
    if recno < 0 then
        tbl.fetch_goto(last_record)
    else
        if recno <=last_record then 
            tbl.fetch_goto(recno)
        else
            ui_msg_box("Error","Record number is past end of table.",UI_STOP_SYMBOL)
            end 
        end if 
    end if 
    
    DIM GLOBAL V2T_Date AS T
    V2T_Date = tbl.eval("Completiondate")
    
    tbl.close()
    
    
    ?V2T_Date
    = 11/03/2011 08:45:00 95 am
    As you can see, it appears to work correctly, however, when I look at the variable list in XBasic Explorer, it shows as: V2T_Date = <variable type 'T'> (instead of the value).

    Subsequently, when I try to use the variable as an argument in a later SQL query, it shows up as 00/00/0000 12:00:00 00 am.

    Arguements.jpg

    Both it and an additional argument now throw errors.



    Might something have changed between build 1995 and build 2095?
    Attached Files

    #2
    Re: Storing a Time Variable

    Code:
    dim tbl as p     
    tbl = table.open("V2T_Msgs")
    dim recno as n 
    [COLOR="#FF0000"]recno = -1[/COLOR]
    'select record number order
    tbl.index_primary_put("") 
    'go to last record in table
    tbl.fetch_last()
    dim last_record as n 
    [COLOR="#FF0000"]last_record = tbl.recno()[/COLOR]
    [COLOR="#FF0000"]if recno < 0 then
        tbl.fetch_goto(last_record)[/COLOR]
    else
        if recno <=last_record then 
            tbl.fetch_goto(recno)
        else
            ui_msg_box("Error","Record number is past end of table.",UI_STOP_SYMBOL)
            end 
        end if 
    end if 
    
    DIM GLOBAL V2T_Date AS T
    [COLOR="#DDA0DD"]V2T_Date = tbl.eval("Completiondate")[/COLOR]
    
    tbl.close()
    
    
    ?V2T_Date
    = 11/03/2011 08:45:00 95 am
    Couple of items that I think are strange.
    V2T_Date = tbl.eval("Completiondate") - is completiondate the name of the field that holds the time value you want? If so then change this to
    Code:
    V2T_Date = tbl.Completiondate
    Prior to that in red I highlighted some of your code.

    You set Recno = -1 then test to see if it is less then zero. Since you never reassign recno to another value it will always be less than zero. there is no real need test and you can save some steps if you eliminate the test. For instance prior to testing the value of recno being less than zero you fetch the last record of the table. Then store the record number of the last record in last_record. Once you determine that -1 is less than zero you then refetch the record with a record number that matchs what you stored in last_record. Since this is the last record and you already fetched it your tbl pointer should still be pointing to that record.
    Andrew

    Comment


      #3
      Re: Storing a Time Variable

      While <tbl>.eval() isn't common to those of us who learned earlier methods it is valid.

      From the wiki <TBL>.EVAL()
      There can be only one.

      Comment


        #4
        Re: Storing a Time Variable

        Thanks Andrew!

        It now seems to be correctly creating the variable and populating the dialog (pictured in previous post), but I still get the errors about not valid 'Time' variables.


        Hmm. I'm starting to think that I may run into other problems as I continue using the app. Is reverting to a previous build as simple as running an old patch?

        Comment


          #5
          Re: Storing a Time Variable

          Originally posted by Stan Mathews View Post
          While <tbl>.eval() isn't common to those of us who learned earlier methods it is valid.

          From the wiki <TBL>.EVAL()
          Interesting would have never thought to use eval in the context of a table pointer. Definitely would save typing when trying to grab multiple fields from the same record.

          Back to the original issue.

          John,
          once you changed the code it is now correctly showing the values in the dialog but when you click Ok you get the error message? Is the dialog a component you built or an alpha5 built one?

          Regarding reverting back to previous builds all you have to do is reinstall the prior build. I would think you would be better off resolving this issue than trying to bury it with a previous version. If in the near future you do have to update to a newer version of alpha5 you will have to tackle this again. That and I am really curious as to what is causing the problem.
          Andrew

          Comment


            #6
            Re: Storing a Time Variable

            Is reverting to a previous build as simple as running an old patch?
            Yes.
            There can be only one.

            Comment


              #7
              Re: Storing a Time Variable

              Andrew,

              The dialog component is an alpha5 built one. (see attached)

              I think I've determined that SQL is not liking the '95 am' part. If I manually edit that out, the process seems to work.

              I think I may be better off going back to the function we created earlier and make a character field in mm/dd/yyyy hh:mm:ss format.

              As I mentioned at the beginning, the process was working fine right up until I did the patch.

              John
              Attached Files

              Comment


                #8
                Re: Storing a Time Variable

                Unfortunately, I didn't have enough time to find a fix so I had to revert to an older version.

                Back on Build 1995 it works fine. I'm going to try to update one build at a time to see if I can identify where it breaks.

                The bad news is, I didn't record and can't recall the version number I was on prior to the update to 2095. Might that be stored somewhere in the registry or elsewhere?

                Comment


                  #9
                  Re: Storing a Time Variable

                  If you found a previous build that works, then it is a bug. Unfortunately since you are using Version 9 Alpha5 will not fix it for version 9. If the bug still exists in Version 11 then they will fix the version 11 build.
                  Andrew

                  Comment

                  Working...
                  X