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

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

Updating Records

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Updating Records

    There probably is a very simple way to do this, but since I'm still learning, I need some help.

    I have two identical databases: Database A has data from a pull from the college system that has had some updated information as well as additional data fields added. Database B is identical to A except that it doesn't have the additional updated fields, but has newer records. The reason I have two identical databases is that database A was an older pull of data (2 months ago and was found to have missing data). It was decided to scrap everything and just start from a fresh pull of current data. However, now that things have smoothed out, they want the old data (database A) merged with the new pull records in database B.

    So, what I want to do is take the data in A's class set and based on course_id, update some of the fields in the new class set in database B so that lots of hours won't be expended manually updating. There are over 18,000 records.

    My question is what is the best way to do this, again, I'm a newbie and am trying to learn all the ins and outs of Alpha.

    Thanks in advance,

    Ben

  • #2
    Re: Updating Records

    I think you want a post operation with the course_id field as the linking field. Most operations work on tables (not sets).
    There can be only one.

    Comment


    • #3
      Re: Updating Records

      Ben, one of the "ins and outs" to master is the distinction between "databases" and "tables". An Alpha Five "database" is sort of like a "project" or an "application". it contains a number of objects including tables. "Tables" are the actual data stores. The "dbf" files, if you will. Here it seems you're really talking about tables, not databases, right?

      Comment


      • #4
        Re: Updating Records

        What I have is actually 2 Alpha 5 V10 databases (each located in its own directory), one called QA and the other called WFD. WFD is an exact copy of QA. Inside of each database there are identical tables (Classes, Instructors and Students). What I want to do is merge/update the Class data from QA into WFD based on the Class_Id.

        Does this help?

        Thanks,

        Ben

        Comment


        • #5
          Re: Updating Records

          Better, but we have no idea what "merge/update" might mean to you.

          Suppose you have a field class_desc in Classes in WFD. That field is empty.

          The same field exists in Classes in QA but has been populated.

          You can design a post operation for Classes in WFD to fill in the class_desc from the field in Classes in QA.

          For example.
          There can be only one.

          Comment


          • #6
            Re: Updating Records

            Hi, Ben.

            Yes.

            As Stan suggests this is going to have to be done one table at a time. You will need to think about how you want to handle:

            a) records that are identical (and how do you define identity?);

            b) records that have the same class_id but different data (which do you keep and which do you discard?);

            c) records that exist in a table in the QA database but are not present in the corresponding table in the WFD database (append ? if so, do you preserve the class_id or assign a new one? How do you avoid overwriting or duplicating an existing record with the same class_id? Are there field rules that must be observed as new records are entered in to the table in the WFD database? auto-increment fields? etc)

            This gets complicated in a hurry, and the same thought process is needed for each table.

            -- tom

            Comment


            • #7
              Re: Updating Records

              I understand what you mean about this getting out of control real quick. Merge/Update to me means marrying data from one source into another. I'll tinker around and see what I can come up with.

              Thanks everyone,

              Ben

              Comment


              • #8
                Re: Updating Records

                Tom and Stan,

                I went in and used the "Post" function and it worked like a champ. Thanks again for your help. I'm slowly digging out of the hole and starting to move forward more productively with Alpha.

                Thanks,

                Ben

                Comment

                Working...
                X