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

Archiving old data, looking for ideas

  • Filter
  • Time
  • Show
Clear All
new posts

  • Archiving old data, looking for ideas

    I have a physically small table, 9 fields, with 160,000 records. A number of the records are outdated as far as current information, but for historical reasons, need to be retained. I wanted to hide the old records just to make it easier to navigate the form and browse. Iím using a logical field as a switch to hide older records. If logical is true, hide.

    While 160,000 records are a lot of records, using this methodology really slows down the performance of the form. Iíve tried using a filtered index. Iíve tried using the filter in the form properties. It doesnít appear to make any difference.

    Without the filter, the form really snaps. With the filter, the form appears to hang. I thought a logical would be the way to go; maybe I should use a character field?



    My other thought was to move all the records to a archive table for reporting purposes and to remove older records from the everyday table.

    Looking for some ideas.
    Alpha Anywhere v3.5
    Version 12.3, Build 2999
    MySql56 & DBF's

    Alpha 4, 5, Anywhere

    Ron Anusiewicz

  • #2
    Re: Archiving old data, looking for ideas

    My other thought was to move all the records to a archive table for reporting purposes and to remove older records from the everyday table.
    That's what I do.
    There can be only one.


    • #3
      Re: Archiving old data, looking for ideas

      I think you would just create an additional report for the archived table instead of bringing the old data into the production table when a user decides they need to view old info. You could also consider moving to a SQL backend if you are not already using and/or filter the data before entering the application. May take a bit longer to load initially but ensures you are working within your defined parameters. (data not older than 6 months or the like)
      Creating Healthcare Work-Flow Solutions Since 2005


      • #4
        Re: Archiving old data, looking for ideas

        My other thought was to move all the records to a archive table for reporting purposes and to remove older records from the everyday table.
        That is also what I do. Deals(for instance) more than so many days old(usually 5 years) are removed to a second table/set. Most of the reports were kept and modified just for the ancient data.

        Easy to do with append, then delete/pack. Once you have it so you know it is happening right, make it automatic. It can always be brought back if needed.

        Some of my dealers have/want to keep records current for 5 or 7 or 10 years, so I made it a global var that is set at the beginning of their sessions. At the end of a session, all old data is gone to the archive set. Tables are names, deals. Trades and inventory are handled a little fifferent.
        Dave Mason
        Skype is dave.mason46


        • #5
          Re: Archiving old data, looking for ideas

          You could also upscale to sql backend, say mysql, shouldnt be too much hustle for you since tables is small (column count).
          INFOMAS (Information Systems)


          • #6
            Re: Archiving old data, looking for ideas

            You could also upscale to sql backend, say mysql, shouldnt be too much hustle for you since tables is small (column count).
            That has it's own good and bad thoughts. To the best of my knowledge, the speed running through alpha is a little less than a dbf and there is the eventuality of a size limit on most sql files(larger than dbf of course). You also have to carry the overhead of a server on the system that does eat some resources somewhere. It is easier to move to the web side with sql, but sql is not an absolute necessity there either.

            Remember the overheads: alpha, microsoft .net, whichever sql, and anything else you have running. Given a machine with tons of memory and space with lots of speed, who cares. My main machine is a 3gig xp3 with 2 gigs of memory and a large hd and it is still a little slow on the start because I also have other stuff running that I have to use.

            I use dbf for my desktop(about 30 apps so far), but would use ms sql if I were doing a web app(and I have). Doing a hybrid(and I have), it would depend on the circumstances.

            There are learned/experienced people on here that do only one or the other. I respect their judgement for their decisions.
            Dave Mason
            Skype is dave.mason46