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

Backorder design advice needed

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

  • Backorder design advice needed

    My wife has a craft business, and she often ships and bills partials. So, I need to add a backorder system to the Alpha Order Entry system, and I,m looking for advice on the best design.

    For example, would you create a new (backorder) order when the order is posted if not shipped complete, or would you use a child table of deliveries?

    Thanks for any help,
    Pat
    Pat Bremkamp
    MindKicks Consulting

  • #2
    RE: Backorder design advice needed

    Pat,

    I think a lot depends on how you're set up now. Which would be the easiest way to show the delayed shipment? Perhaps a logical field to mark an item as delayed shipment and then uncheck it when it's shipped.

    You could easily create a query or whatever to show which customers's orders have been delayed. I wouldn't make it any more detailed than necessary. Keep it simple.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


    • #3
      RE: Backorder design advice needed

      I have a client who sells merchandise on the internet. We daily get data from AuctionWorks and MonsterDotCom in excel files. I import the data and then process orders.

      When an order cannot be filled, I write the backorder to a matching "backorders" table.

      Naturally, inventory parts available is the key to the backorders. So when he gets new product delivered, it updates the inventory table.

      When the system processes orders, it appends backorders to current new orders, (empties the backorders table,) and processes back orders with the highest priority.

      When daily process orders completes, it creates and prints a picking list, for staff to pull items, gives him the opportunity to correct inventory count, and reprocess.

      When finished, it writes to backorders all unfilled orders, and sends the data for shipping to UPS and USPS software that prints mailing labels with postage, assigns tracking numbers, etc.

      When finished the postage software sends the data back, his alpha software looks for incomplete shipping info, etc., and then emails are sent to all clients with date sent, via, tracking numbers, etc.


      Cole Custom Programming - Terrell, Texas
      972 524 8714
      martin_w_cole@msn.com

      ____________________
      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

      Comment


      • #4
        RE: Backorder design advice needed

        Martin,

        Thanks. You brought up some very good points.

        Your procedure sounds excellent, but my wife's business doesn't have that kind of volume yet. So, for an interim step, I think I'll also take Ken's advice and just make the new order directly into the order table. I'll add a logical field "BackOrder" and a "FromOrder" field so she can track back to the original order if she needs to, and I can use the BackOrder field and Order dates to prioritize the picks. This sounds easy enough that even I can figure it out!

        Thank you both for all your help.

        Pat
        Pat Bremkamp
        MindKicks Consulting

        Comment


        • #5
          RE: Backorder design advice needed

          read this by bill warner from a recent alpha newsletter

          http://newsletter.alphasoftware.com/0040203.htm

          Comment

          Working...
          X