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

Order of Appended Records? (For Web Login Data)

  • Filter
  • Time
  • Show
Clear All
new posts

  • Rich Hartnett
    Re: Order of Appended Records? (For Web Login Data)

    As always, "Stan you are the man!"

    That works great, thanks.

    Leave a comment:

  • Stan Mathews
    Re: Order of Appended Records? (For Web Login Data)

    tst = " - 05/February/2013 06:41:06 11 pm - USERID: denig - LOGIN EXPIRES: 05/February/2014 06:41:06 11 pm"

    ? word(alltrim(word(tst,2,"-")),2," ",3)
    = "06:41:06 11 pm"

    Or if you want a a shorttime value

    ? ctot(word(alltrim(word(tst,2,"-")),2," ",3))
    = 06:41:06 11 pm
    Last edited by Stan Mathews; 11-25-2013, 02:13 PM.

    Leave a comment:

  • Rich Hartnett
    Re: Order of Appended Records? (For Web Login Data)

    Hey Stan that works great. How about one for parsing the login time portion?

    06:41:06 11 pm

    (The result could be in military time if necessary.)

    Leave a comment:

  • Stan Mathews
    Re: Order of Appended Records? (For Web Login Data)

    Looks like Alpha has some sophisticated coding in ctod()

    tst = " - 05/February/2013 06:41:06 11 pm - USERID: denig - LOGIN EXPIRES: 05/February/2014 06:41:06 11 pm"
    dttm = alltrim(word(tst,2,"-"))
    ? dttm
    = "05/February/2013 06:41:06 11 pm"

    ? ctod(dttm)
    = {02/05/2013}

    Leave a comment:

  • Rich Hartnett
    Re: Order of Appended Records? (For Web Login Data)

    Well actually the initial data that comes from the Web Application Server is one single line of text: - 05/February/2013 06:41:06 11 pm - USERID: denig - LOGIN EXPIRES: 05/February/2014 06:41:06 11 pm

    When I append this data to the second table, I keep the original text above, but then use expressions to break it up into separate fields. The date field ends up being a character field which displays this: 05/February/2013 06:41:06 11 pm

    Leave a comment:

  • Tom Henkel
    Re: Order of Appended Records? (For Web Login Data)


    is the date/time field an actual date-type field? Or is that "05/February/2013 xx:xx:xx" a character field? If it is a character field, then I think you're going to have to do some sort of brute force conversion to get it into a "standard" date-type field.

    Once that is accomplished, you could order it with the following:

    which should put it into ascending order by date/time.


    Leave a comment:

  • Rich Hartnett
    Re: Order of Appended Records? (For Web Login Data)

    ** UPDATE ** (I answered my own question, but it doesn't solve the problem.)

    After some experimenting I found that the changing of the appended records is due to the fact that I am only appending unique records. Apparently in its test for existing records, it then appends only the new records, but does so in an ascending order.

    So to combat that, I think I will display the records in a web grid, and force them to display in "date order." The problem now is that the date is not in a valid date format, so I need to convert it.

    Is there an easy expression that would convert the following date and time text to a normal date/time (XX/XX/XXXX) type that I could parse into separate fields?

    05/February/2013 06:41:06 11 pm
    Attached Files
    Last edited by Rich Hartnett; 11-21-2013, 06:10 PM.

    Leave a comment:

  • Order of Appended Records? (For Web Login Data)

    I'm using a simple Import operation to gather my user's login data from the Application Server's log file source.

    I then append it to a second table that I use to parse out the data to make it easier to read.

    The problem is that while the import table has the log records in the correct order that they were gathered by the Application Server, when I append them to the second table, they are in ascending order based on the data of the first field (IP Address).

    The first picture below shows the imported records, the second picture shows how it ends up looking after being appended to a second table.

    Is there a reason why they are not appending in DBF record order? I want my final appended table to stay true to the logical order that they were entered into the server.

    Last edited by Rich Hartnett; 11-21-2013, 05:05 PM.