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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Index Selection For Append

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Index Selection For Append

    Can the index be specified for the transaction database
    during an append operation?
    Tags: None
    #2
    RE: Index Selection For Append

    I don't think so.

    I see nothing in the parameters to the tbl.Append() operation which permit one to specify an order expression for the transaction table.

    In testing here it seems this operation always appends records in their natural or 'record number' order.

    May I ask why appending in a particular sequence would be of use to you?

    -- tom

    Comment

      #3
      RE: Index Selection For Append

      I would like to process the transaction database in
      inverse record number order during the append operation.

      Currently, I accomplish this by building an inverse
      copy of the transaction database and then using the
      inverted copy as the transaction database for the
      append operation. The "copy" step could be skipped
      if an "invert" index could be used during the append.

      Comment

        #4
        RE: Index Selection For Append

        It's clear you want to control the order of the transaction table, as the append is done. What's not clear is why? I believe that the receiving table's indexes will automatically be updated as records are appended, so it's not clear to me why having them arrive in a particular order is useful. How would it make a difference?

        -- tom

        Comment

          #5
          RE: Index Selection For Append

          The associated application tracks the movement of case
          files among various work locations in the municipal
          court. These files are identified by case numbers.
          When files are moved information related to the action
          is captured by means of a scanner and the information
          is stored in a database.

          The database contains the movement history for the files
          and the latest entry for a case number identifies the
          current location of the files. Numerous entries can
          exist for a particular case number.

          We run a background process which requires a database
          that contains only records which identify the current
          (i.e., last) location of a case file. This database is
          created by reading the original database in inverted
          order and appending the data to an empty database. The
          process rejects duplicate case numbers so the new
          database contains only records which identify the last known location of a case file.

          Comment

            #6
            RE: Index Selection For Append

            I see. It's not the order in the Master table that alone is critical. It's the combination of the order in the transaction table and the process which ignores duplicate case numbers which serve as a sort of 'filter' for the Master table. Your design attributes meaning to the position of a record in the transaction table. If it's the 'last' one, then values in that particular record match the current physical location of the case file.

            The whole thing would be easier if you could add a field to each record in the transaction table. Make it logical, and name it 'currentlocation'. Set it true whenever a new movement transaction occurs, re-setting others for the same case to false. Then your append is simple as pie. Just filter on currentlocation.

            In addition to the process you currently employ, the only other way that occurs to me would be to write an xbasic script which copies the last 'movement' transaction record to a second table. The receiving table could be zapped after each use, and used over and over... This would save creating the temporary table from which you are currently basing your append. If this is of interest drop me an email note, and I'll lend a hand.

            -- tom

            Comment

            Previous template Next
            Working...
            X