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



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

Header & Items Mismatch

  • Filter
  • Time
  • Show
Clear All
new posts

  • Header & Items Mismatch


    I'm running into instances of where I can have an Invoice Header with no Invoice items attaced to it. Normally, this happens when I have a brand new user, and there are no records associated to that user. Anyway to avoid "orphan record creation" from the header and line items when this happens ??


  • #2
    Re: Header & Items Mismatch

    Sounds like you have a parent and no children... not an orphaned child record. In any event the answer to your question is yes, but we'll need to see your app and you'll need to furnish keystroke by mouseclick instructions for us to mimic the data entry sequence your user is following to create the problem.


    • #3
      Re: Header & Items Mismatch

      You could avoid printing blank invoices by filtering with a "scanning" option. Scanning tests to see if there are any child records at a specific level of the set. If none, don't print the invoice.



      • #4
        Re: Header & Items Mismatch


        I've attached a sample of the database. The scan login is "rsw123" from the main menu.

        From there, go to "Tool Return", and select "Tool Std Return" passord is "123456".

        From the drop down, select any of the first 3 inventory item (from the Product) table, and this is where it appears to create the blank records into the Product table.

        Thanks again for any insight as to what this occurrs.
        Last edited by [email protected]; 04-19-2009, 09:49 AM.


        • #5
          Re: Header & Items Mismatch

          In your invoice header table the Invoice_Number field is C:14 whereas in the Invoice items table the Invoice_Number field is set to C:6

          Also in the product table field rules for product_id you have the data entry set for "always Required" AND you have a custom validation set as well. I removed the custom validation and it seems to work.


          Glen Schild

          My Blog


          • #6
            Re: Header & Items Mismatch

            Thanks will give it a try, and let ya'll know. Ryland


            • #7
              Re: Header & Items Mismatch

              I tried what you suggested, and I'm still getting a blank record that keeps getting written to the Product file....It's weird because you would have thought that the field validation rule would have prevented that, but why I don't get the same behavior on the Invoice entry screen is beyond me... What I do is then go to the Product file and with an assending sort, the blank record appears...
              Last edited by [email protected]; 04-19-2009, 03:24 PM.


              • #8
                Re: Header & Items Mismatch

                I did notice that there were a couple of blank entries in the product field. Try deleting those and have another go.
                Glen Schild

                My Blog


                • #9
                  Re: Header & Items Mismatch

                  Yes, I just delete those. retied. Noticed that the same think happened.

                  What I just did however, was to remove a couple of msgbox's in the return and then added an additional button to commit the record at the end. The first run appeared to be ok in not generating the additional blank record in the product field....will continue testing and let everyone what we find out.




                  • #10
                    Re: Header & Items Mismatch

                    Problem solved. I added a forced save - commit at the end of the return record, and removed the display messages that were appearing.

                    Thanks for everyone's help.