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

Got to be a simple solution

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

    Got to be a simple solution

    I am designing a database to enter repair orders on heavy equipment.

    I am using a table called "service_log", set up like invoices in Alpha Sports.

    From the service_log table the equipment_info is looked up and linked to the part_ numbers table in a browse, just like invoice items in Alpha Sports, called service_log_items.

    This eliminates reentering recurring part numbers across different equipment and eliminates attaching an equipment name to each part.

    I would like embed a browse to list all unique part numbers on a form for a specific piece of equipment.

    I have tried several combinations of sets to link equipment_info to part_numbers.

    Bob
    Tags: None
    #2
    Re: Got to be a simple solution

    Robert, that's a good overview. Now how about some details, using actual table names, positions in sets, linkage types and specs (if any)? Use actual names. There is no table in AlphaSports called "invoices", for example. What do you mean by a link to a part_numbers table in a browse? Are you really talking about a table lookup field rule? The devil is in the details, which, so far at least, are pretty opaque. You will find that writing this kind of thing will be tedious and time consuming, but necessary in cases where you can't post a working sample of the database itself. Posting a working sample of the database is always the best course, since readers can explore all necessary details themselves, minimizing communication difficulties.

    Comment

      #3
      Re: Got to be a simple solution

      Hi Robert,

      You will need a child table of all the parts. Each record will have a field that is the "part number" for the Equipment.

      This table can be linked 1:N, to the set you are making the service order for.

      If the customer has a number of pieces of equipment you should be able to filter that list, when you do the lookup, to show only the equipment they have.

      Sample data is always better to work with.
      Regards
      Keith Hubert
      Alpha Guild Member
      London.
      KHDB Management Systems
      Skype = keith.hubert


      For your day-to-day Needs, you Need an Alpha Database!

      Comment

        #4
        Re: Got to be a simple solution

        Tom,

        The setup is completely like the Alpha Sports database. The invoices table that I referred to is "invoice_header.

        In the case of the Alpha Sports database, I am trying to generating a form with the customer table and embedding a browse showing all unique products for that customer.


        Bob

        Comment

          #5
          Re: Got to be a simple solution

          Originally posted by Butchy View Post
          Tom,

          The setup is completely like the Alpha Sports database. The invoices table that I referred to is "invoice_header.

          In the case of the Alpha Sports database, I am trying to generating a form with the customer table and embedding a browse showing all unique products for that customer.


          Bob
          Bob

          I know your explanation makes sense to you, but - like Tom said - we're missing some details.

          Do these products repeat on a single invoice or are you looking for all unique products that a customer has ever been invoiced? Or is it just for the last year or all the time that the customer has done business with you?

          Or is it door D (another option)?

          Is a form really needed or is a report sufficient?
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment

            #6
            Re: Got to be a simple solution

            Bob, there's no easy way in AlphaSports to show all unique "items" that a single Customer has ordered using a form that contains a browse object displaying the items. One would have to alter the structure of the items table to include a foreign key so the items table could be linked to the Customer table using the Customer_id. This creates a bit of redundant data in the Items table, but ... perhaps it's the solution you're grasping for?

            Comment

              #7
              Re: Got to be a simple solution

              Tom,

              I will try that first.

              I should have started by stating the end result:
              I want the customer to review all parts that have been used in repair orders (service_log) on a specific piece of equipment. If that must be a report, that is fine.

              Comment

                #8
                Re: Got to be a simple solution

                Hi Robert,

                A report sounds just what you need.

                Group "specific piece of equipment" within a group for Customer. Then Parts used in the Detail section.
                Regards
                Keith Hubert
                Alpha Guild Member
                London.
                KHDB Management Systems
                Skype = keith.hubert


                For your day-to-day Needs, you Need an Alpha Database!

                Comment

                  #9
                  Re: Got to be a simple solution

                  Originally posted by Butchy View Post
                  Tom,

                  I will try that first.

                  I should have started by stating the end result:
                  I want the customer to review all parts that have been used in repair orders (service_log) on a specific piece of equipment. If that must be a report, that is fine.
                  Sounds like you should start with a report.

                  Since you have posted this in the desktop forum, are you going to email-snailmail these reports? You can do either or both.
                  Al Buchholz
                  Bookwood Systems, LTD
                  Weekly QReportBuilder Webinars Thursday 1 pm CST

                  Occam's Razor - KISS
                  Normalize till it hurts - De-normalize till it works.
                  Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                  When we triage a problem it is much easier to read sample systems than to read a mind.
                  "Make it as simple as possible, but not simpler."
                  Albert Einstein

                  http://www.iadn.com/images/media/iadn_member.png

                  Comment

                  Previous template Next
                  Working...
                  X