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

appending records from set to set

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

    appending records from set to set

    I have a set that I want to archive records from at chosen intervals. The set has a parent table with 4 child tables, and one of those has a child which also has a child. I want to somehow mark a record in the parent table, and then be able to append that entire record to a set that has the exact same structure, then delete that record from the original. I read an example on learn alpha.com, but I am not sure that that will work for what I want to do. I want to be able to mark the record, and by marking it also have all the child records associated with that parent also marked. Once that is done, I could setup multiple append operations, one for each table, and have them all run in sequence, then run a delete operation the same way. Is that the best way to do this? Any help is appreciated.

    Todd
    Tags: None
    #2
    RE: appending records from set to set

    Todd,

    What if you arranged both sets so that you didn't have to delete anything except change the value of one field that would cause records to filtered from the active set.

    Idea: have a logical field named tablename->archive, whereby if the field value of archive = .N. the record is displayed in this set, the Active set. If you change the value of that field to .Y. then filtering doesn't allow it's display in this, the Active set, but will be filtered to be seen only in Archive set. Your filtering on your old/archive set would be the opposite of your active set. The only records allowed to be displayed would be those where archive = .Y.

    Also, maybe it would be possible to only have one set whereby you have a button Active and another Archive, press the button Active and only active records are displayed. Press the Archive button and only Archive records are displayed.

    Would a two state radio button help with this one?

    Mike
    Thank you,
    Mike Konoff

    Comment

      #3
      RE: appending records from set to set

      I had thought of something like this, and it may work great. The only question I have is will the size of the data in this set someday be a problem? Right now there are at most 200 records in the parent, with anywhere from one to 25 or so records in each child linked to one parent.

      Comment

        #4
        RE: appending records from set to set

        A consideration is where you'll be appending a duplicate of a child. One example would be in an order system where a client is already in the archive and subsequently places another order. Another would be an item in an inventory table.

        First make a safety.

        Another approach might be to first copy certain child records to overwrite those in the archive (customers, clients, inventory, etc) where they are primarily support files where you don't want duplicates (otherwise when you do the append for this type of table make sure you over-write the existing older outdated record in the archive).

        Then copy transaction/parent tables, etc to another directory. Mark all records for deletion that you don't want in the archive (for example, those that are no more than 3 months old), pack the table, and then append them to the archive. This can all be done using XBASIC (probably best from a form outside of the tables you want to archive, using table.open()). The reverse can be done to eliminate old records from your main operational table(s) (amke sure to add table.pack() to the operational table).

        This way all your support and lookup tables can be kept current, without duplicate records except where you don't want them, and transaction tables can be updated in the archive and current set. The entire operation can probably be run from 1 form.

        If you want to keep the archives on-line for access you only really have to update the transaction tables since the lookup/client/customer/etc tables can be kept live in both sets. Just start with copies of the transaction/parent tables, with different names, and create new sets based on them. Making safeties/back-ups and archiving them will also take less space.

        Comment

        Previous template Next
        Working...
        X