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

Master List

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

    Master List

    I do baseball and basketball registerations for our organization. They have ask me if I could make a master list showing both baseball and basketball people who are registered. Some of the kids play both sports. I'm a real novice at this. I have one db for baseball and one for basketball. How would I go about making one master from both db's.? I just need their name and address. Any help would be much apprecieated.
    Thanks,
    Dave Fraser
    Tags: None
    #2
    RE: Master List

    Try Operations-New-Join

    That will allow you to mix data from two tables.

    You could also do it with Operations-New-Post.

    There is a small example you can view to make sure that's the function you want. It's viewable after you select Post or Join (you can back out at that point if you don't want that function.)

    Comment

      #3
      RE: Master List

      Dave, There are a number of ways to do this. The easiest way I can think of is to append both tables of registered members into third table. Then run a delete dups operation. The kids who play both sports will be initially entered twice in the third table but if you run a delete dups operations you will end up with one clean table of all.
      If you are familiar with the append operation you could cut out the delete dups step by having the second table that appends ignore a record if it is a duplicate. Either one is pretty simple.
      Jeff

      Comment

        #4
        RE: Master List

        Jeff,
        As I said i'm a real novice at this. When you say append both tables, do I start a different table called say Master List. Or, do I use the baseball or basketball one to append. Could you explain how I do this. I'm sure anyone reading you reply would know what to do. What I'm asking is could you step me through this (if at all possible)? If you can't I want to thank you for your reply anyway, I'll try to hack through it.
        Again many thanks,
        Dave

        Comment

          #5
          RE: Master List

          You will need to create a new table to append to. You can name it anything you want. An easy way to do this is to right click on either one of the transaction tables and chose duplicate. You will probably not need any field rules and you do not want to duplicat records when asked, as you will only be using this third table to view or print info. Once you have created your new table you can use the append Genie to create append operations for both transaction tables. Just select the fields you want to append. You will want to use replace or ignore for duplicate settings. In other words if the operation finds an existing record already in the master table it needs to know whether to add, replace, or ignore the duplicate record. This way you don�t have to clean the master table out after each append. The master table will only be updated with future appends and will retain a history of all records ever appended. You can however clean up the master table by zapping it if you want after you are finished. By zapping the table you would not be storing any records that have been deleted in the transaction tables and are no longer active. You will have to decide what you which one fits your needs.
          If you want to email me the two dbf's for the transaction tables I'll whip up the stuff for you.
          Jeff

          Comment

            #6
            RE: Master List

            Dave,

            It's not unusual to start out by having two tables for two different groups of people, but I agree with everyone here that since the main distinguishing factor between them is the sport that they play. I would also keep them all in one master list and then remove the dupes.

            However, I would also add a field to the new table (e.g. "SPORT") that would contain codes for the sports that each individual played. An old but easy way would be to have a simple character field that contains a single letter code for each sport. Those that played both sports would have both code letters in that field -- those that didn't would only have the applicable letter in theirs.

            When you query, you can select records with either or both codes. It isn't elegant, but it works well for situations where you don't require more than 26 codes and each record can qualify for a variety of combinations thereof...

            Best regards,

            Geoff Hollander

            Comment

              #7
              RE: Master List

              I agree with Geoffrey that you need to identify the individuals, but I've found it easier to handle if you set up a separate field for each sport. Then you can simply search for those whose field so-and-so is not blank.

              Alpha-5 is wonderful for this kind of manipulation. It's quick, easy, and really does the job.

              As an example of the above, I recently had to merge information from 9 different data bases - all with different numbers of fields and different kinds of identifications. I created an empty master .dbf, made sure that it had all the fields that were in all of the separate constituent data bases. Then I added an ident field to each individual .dbf, using the name of that .dbf. Then I appended each of the constituents in turn to the master - making a 100% copy with no concern for dupes or whatever.

              Now I had a master with everyone included, and with identification of which .dbf he came from. After that, you can go through the usual marking and/or deleting for dupes, etc. Sometimes you want the data from one particular source to stay in preference to the data on the same person from another source, and it's easy to make the distinctions and to specify the choices.

              Good luck. It gets easier and quicker the more you do it.

              Leon Brachman
              [email protected]
              817-877-3003
              fax 817-877-3155

              Comment

              Previous template Next
              Working...
              X