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

Posting Operation Corrupting Data

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

    Posting Operation Corrupting Data

    I have an Iventory - invoicing program to track and bill materials used. Recently I wanted to change the ID codes in my inventory table and then I needed to update the invoice detail records to maintain the link on the past records.

    I started by adding the new id fields to both tables. I then assigned new unique ids to the inventory. I now had both the old and new ID's in the inventory and the new id field in the invoice detail table which needed to be updated with the new inventory id code.

    I created a "posting operation" where the master file was the invoice detail table and the transaction file was the inventory table. I matched on the old ID and replaced the master table new ID with the transation table new ID. This worked exactly as expected with all id fields properly filled in.

    THE PROBLEM is that the invoice number field was blanked out on over half of the records in the master table. This destroyed the link between invoice header and invoice item table. There was no reference to this field in the posting operation definition and there should have been no change to this field. These two tables were opened by themselves and not part of a set. The invoice detail table does have multiple occurrances of many of the inventory items but they all updated properly even though Alpha steps through the transaction file instead of the master file.

    QUESTIONS:
    1> Has anyone else had this problem?
    2> Am I using the posting operation improperly?? It worked fine on the fields called out in it. I got the results I expected in those fields.
    3> Is this problem new in version 4.5

    Input anyone?

    Dan
    Tags: None
    #2
    RE: Posting Operation Corrupting Data

    Dan, sounds to me as though you would have had better results using an 'update' operation, instead of a 'post'. Using an inverted set, with one to one links, you could replace the blank field with the new value, based on the value found in the matching child table record. (INvoice detail records are the parent table, inventory table is the child, in my scenario.)

    -- tom

    Comment

      #3
      RE: Posting Operation Corrupting Data

      Tom,
      I didn't see an option to update records based on data from another table but then I wasn't working with a set either. I guess that if you did an update based on a set you would be able to do it. I just thought it would be easier (simpler) to step through without creating a temporary set and I still don't understand why it corrupted fields that were not involved. That field should not have been altered.

      I Will try the set method using an update operation as I would rather step through the master than the transaction. I don't know why I didn't see that on my own. It's really quite a simple solution. (kinda the forest for the trees dilema)

      Thanks for your input...

      Dan

      Comment

        #4
        RE: Posting Operation Corrupting Data

        Tom,

        I tried the update operation on a set with a one to one relation and stepped through the Invoice detail file updating with info from the inventory file. ID's were updated as expected again but 3900 +/- records had their invoice numbers blanked out still.

        I need to get to the bottom of this. I'll try a couple of things and then may send the files to see if others get the same results.

        At a loss...

        Dan

        Comment

          #5
          RE: Posting Operation Corrupting Data

          Dan, here's something to check. Do you have any field rules in place that manipulate or validate the fields involved in these operations? How about the field which is being inexplicably blanked out? If so, maybe you ought to disable the field rules before running the update operation.

          Otherwise, posting it here will give us a chance to help. If privacy is an issue feel free to email it to me. (After zipping it first, please).

          In either case, I urge you to include a text file 'readme' explaining the situation and your goal in detail.

          -- tom

          Comment

            #6
            RE: Posting Operation Corrupting Data

            Yep!

            That's what it was alright. My invoice number field is a calculated field based on a sub string of the link field so that I could link multiple fields in the child records to the parent record link. This was a revision sometime back so all records before that point were missing that string.

            Funny how the computer does just what you tell it to. It was a memory lapse on earlier modifications to the system. Must have been a senior moment...

            Anyway, thanks for your input. This message board is a wealth of info.

            Dan

            Comment

              #7
              RE: Posting Operation Corrupting Data

              "Funny how the computer does just what you tell it to."


              Agreed. My pc is not very intuitive!


              -- tom

              Comment

              Previous template Next
              Working...
              X