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

Multiple Ship To

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

  • Multiple Ship To

    I would to over ride the default Ship To field on the invoice to a lookup list showing all Ship To for that customer. Some have over 100 Ship To. I do have a Ship table that is linked to the invoice.

    Thanks,

    Jay

  • #2
    RE: Multiple Ship To

    Hello Jay:

    I'm not quite sure what you're asking. However, let me make a couple of general comments reference default field values.

    You can manually overide any default value.

    You can also create a default lookup value to another table, such as your "Ship" table.

    Robert T.

    Comment


    • #3
      RE: Multiple Ship To

      Thanks Robert for your reply.

      What I already have is a ship table on my invoice. When a record is entered on the invoice the default ship address is entered into the ship field. what i would like is a button placed beside the ship field that opens a Lookup form that displays all "Ship To" addresses for that customer. The Ship value would come from the same "Ship To" table. I would then choose which Ship address to enter on the invoice.

      Once again thanks,

      Jay

      Comment


      • #4
        RE: Multiple Ship To

        Jay,

        If it were me, I'd remove the Ship To table from the set your invoice form is based on.

        I'd then define a table lookup in field rules for the invoice_header table (or whatever table you're using for the ship_to fields). The table lookup field rule would be defined to link on the Ship_to field, but would fill in automatically the Ship_to_city, Ship_to_State, and ship_to_zip fields.

        The user guide has an example, in the chapter on Field Rules. It's basically set up the same way you'd do one in Alpha Four.

        -- tom

        Comment


        • #5
          RE: Multiple Ship To

          Thanks Tom and Robert,

          Problem solved. I deleted the Shipping table from my Invoice per your recommendation. I then created the appropriate shipping fields in the invoice header. Using the field rules on the invoice header I set the “Lookup” to table “Shipping” and linked necessary fields together.

          The only other issue I am facing is filtering by customer. Most of my customers have multiple ships to addresses. In the shipping table I have a field for Customer Id. I use the same ID for shipping that is used for Billing. If a customer has 10 Ship To addresses, all the addresses have the same number.

          Here is the order for how I would like to accomplish this. After the invoice is open the customer is selected. Then in the shipping field the “Shipping” Lookup displays the shipping address for that customer. By using the Customer ID in the Billing table all addresses with the same Customer ID in the shipping table are displayed.

          I tried using the code editor on the field rules but to no avail. Any help would be appreciated.

          Also, I would like to apologize because I placed this thread in the wrong form. I am using Alpha 5, not upgrading. I had hoped that this solution to this problem would be of help to other new Alpha 5 users.

          Regards,

          Jay

          Comment


          • #6
            RE: Multiple Ship To

            Jay:

            Glad to see that your initial problem was resolved. Tom Cone is one of the sharpest people on our forum. He almost always gives excellent advice. In addition, he is also one of the nicest people you will find anywhere.

            As for your customer shipping address problem, a couple of years ago I wrote an application which I think had a similar problem reference. When I have some free time, I'll try to remember and look up that database to see how I solved that problem, assuming it was the same one.

            Robert T.

            Comment


            • #7
              RE: Multiple Ship To

              Jay:

              I’m not saying this is the best or the preferred solution, but let me tell you what I did a couple of years ago for one of my customers and it worked like a charm.

              Each customer has a UNIQUE Cust_ID number.

              Each customer also had multiple shipping locations that are stored in the ShipTo table.

              There are many fields in the ShipTo table, but we’re only concerned here with the first 3 fields in the table. Those first three fields are used to create a unique Ship_ID for each one of the company’s shipping addressees. Remember, the key field in this table is the third one, the unique Ship_ID field.

              The first field in the ShipTo table is the Cust_ID number.
              The 2nd field in the table is a unique Number [AutoIncrement Field Rule]
              The 3rd field is a calculated field called Ship_ID which combined the value of the first two fields. Let me give you an example.

              Cust_ID 001 is the PA State Police and Cust_ID 002 is the NY School System. Here are some entries that would go into the ShipTo table.

              First 3 fields of the ShipTo Table

              Cust_ID Ship_No Ship_ID Location
              001 0001 001-0001 Philadelphia
              001 0002 001-0002 Pittsburgh
              001 0003 001-0003 Lancaster
              002 0004 002-0004 Brooklyn, NY
              002 0005 002-0005 Queens, NY
              002 0006 002-0006 Bronx, NY

              The Invoice form has a Ship_ID field, which had a table lookup Field Rule in the ShipTo table. Select the correct Ship_ID and all of the shipping address fields are automatically filled in.

              So each one of the shipping addresses for a company has a UNIQUE Ship_ID field. But you can query and report on the customer by using the LEFT 3 numbers of the Ship_ID field, which will always identify the customer.

              Remember, use an Auto Increment Field rule for the 2nd field in the table, the Ship_No field. Than make Ship_ID a calculated field combing Cust_ID + Ship_No.

              I’m sure someone else can some up with something better, but as stated above, this worked perfectly.

              Robert T.

              Comment


              • #8
                RE: Multiple Ship To

                Hi Robert,

                Once again thanks for your help and the example. I am impressed with your knowledge and understanding of data and how all the pieces fall together. It shows and teaches me to dig deeper and create more flexible applications.

                My only concern now with your example is my customer Id field is a character field and not Number. It is my understanding that you cannot do calculations by mixing character and number fields. I would revert to using number fields for customer ID’s but all my customers already use charters and numbers combinations in their I.D.

                Is there anything in the Expression Builder that can bring focus to the customer ID in the Bill To and then when the shipping lookup is opened bring up all ship to with the same customer number?


                Thanks,

                Jay

                Comment


                • #9
                  RE: Multiple Ship To

                  It is highly recommended that all of your Customer ID and Ship ID and/or similar fields, should be CHARACTER fields. I cannot imagine doing any calculations on a Customer ID or a Ship ID field. So it seems as if you are doing fine in that area, there is no need to convert them to numeric fields.

                  As I said in the previous message, in my particular application, all of the Unique Ship_ID numbers are prefaced by the 3-digit Cust_ID number. For example,

                  001-0051, 001-0052

                  003-0062, 003-0063, etc.

                  It is a trivial matter to query all Ship_ID's by using the LEFT(Ship_ID,3) function, to extract the Cust_ID number, which is the first 3 digits to the left of the hyphen.

                  Does this make sense?
                  Robert T

                  Comment

                  Working...
                  X