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

ARCHIVE RECORDS BUT KEEP CUSTOMER HISTORY

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

    ARCHIVE RECORDS BUT KEEP CUSTOMER HISTORY

    I WOULD LIKE TO ARCHIVE INVOICES AND LINE ITMES FOR MY APPLICATION TO MAINTAIN THE TABLES EASIER AND CONTROL THEIR SIZE. HOWEVER, WE KEEP A CUSTOMER HISTORY THAT IS VERY FREQUENTLY USED, AND I WANT IT TO SHOW ALL TRANSACTIONS INCLUDING THE ONES THAT WOULD BE ARCHIVED. COULD I MAKE A CUSTOMER HISTORY SET THAT WOULD LOOK AT SEVERAL DIFFERENT TABLES (SAY ONE FOR EACH YEAR ARCHIVED)?
    Tags: None
    #2
    RE: ARCHIVE RECORDS BUT KEEP CUSTOMER HISTORY

    mikki,

    I've thought along these lines, but haven't done anything like this yet. FWIW, I was thinking of archiving the old invoices - say over a year old and fully paid. Then when I wanted to see everything together I'd write the archive to a temporary table followed by the current to the same table and then produce the report from the temporary table.

    Another way is to leave all records in the existing table and then write just what's needed to a temporary table (current records and/or old records) and produce the report from the temporary table.

    Hope this helps jog the thinking process.

    Comment

      #3
      RE: ARCHIVE RECORDS BUT KEEP CUSTOMER HISTORY

      You could predefine the archive tables, and include them in your set. Then, you could have an embedded browse for each table. This way, you could see transactions for each year.

      The disadvantage is that it would be difficult to have a report that would include all records. Ohlen's idea would help you in that regard.

      Comment

        #4
        RE: ARCHIVE RECORDS BUT KEEP CUSTOMER HISTORY

        Mikki,
        I went down the archive history route once for the very same reasons, but went back to the single table approach after struggling with it for a couple years for several reasons:
        1. I kept making changes to the file structure as I found more information that I wanted to keep. When this happened, I had to change the structure on all the other tables also.
        2. I found that the archive and delete records process was prone to error, then soon I had duplicate records in both files, for example an item is returned so the record has to be moved from archive to active, then back again.
        3. I also found that there are good ways to speed up an application by avoiding some kind of operations and using indexes for lightning optimization. I have over 170,000 records in my main table and no speed problems.
        4. Archives that store by year are even worse, because there are orders that start in one year, but aren't complete until the next...so which year do they belong in?

        So, for maintenance, control and speed reasons, I recommend a single table.
        Pat Bremkamp
        MindKicks Consulting

        Comment

          #5
          RE: ARCHIVE RECORDS BUT KEEP CUSTOMER HISTORY

          I think Pat pretty well sums it up. I see no need to archive for the sake of archiving. Although not near as many as 170,000, I have an every so often need to look at the stuff I've had for 10 years.

          kenn
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment

            #6
            RE: ARCHIVE RECORDS BUT KEEP CUSTOMER HISTORY

            Hi Mikki,

            If this works right, you will find a script attached here that will
            subtract last years records and put them in a table whose name is
            Y+previous year. Example: This year it subtracted records for year 2000
            and placed them in a new table named Y2000.

            Lotsa O' Luck
            efs

            Comment

            Previous template Next
            Working...
            X