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

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

How Can I do That

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

  • How Can I do That

    Sorry but I really could not find an appropriate title. I need the capability in my database to look at a product and also see its specification. I could have 100 products , these could be broken into say 5 categories and there is sufficient commonality within a category that they can share a common specification.

    How so? lets take 3 example Apple Juice, Ice Cream and Frozen vegetables.

    For ice cream my spec includes: Sweetness, % fat, total solids, total bacteria , % overrun, Storage Temperature and Shelf Life.

    For Apple Juice its: % sweetness, %acidity, Brix/Acid Ratio, Colour, storage temperature and Shelf life.

    For frozen vegetables its : Colour , % foreign matter, Tenderometer, total bacteria, coliforms, storage temperature and shelf life.

    How would I put together a table(s) to manage this or do I need a table at all? There is a tableproducts that carries the product names and product ID numbers.
    Hope this makes sense.
    Thanks for your help.

  • #2
    Re: How Can I do That

    Hi,

    What you seem to be pondering on is usually referred to as "lookup tables" I think, i.e. tables used to store all varieties of a property that tend to recur regularly for items in other tables.

    Which of the fields to create lookup tables for really depends on the kinds of values you expect, i.e. do you want to be able to enter any of a large range of values/numbers, or do you want to limit the user's selections to a set list of selections or ranges (of values for example)?

    For example colour would be something you would probably want to define a set list of colours for in a lkup_colour table (can always add more but it is up to you what they can select), so you can run reports on it by colour rather than having to deal with different spellings and so on of what is really the same word.

    For things like storage temperature or %fat etc, you probably need to be more flexible so you need to let the user enter a number of their choosing, and do any grouping by ranges of values in the individual reports (e.g. group by percentage of fat with increments of 10% or something).

    Comment


    • #3
      Re: How Can I do That

      Thanks, the range of values will be small, specific and similar albeit not identical within a category. So For Apple Juice:

      % sweetness = 10.7 -11.3 , Acid = 5.2 , Colour =18-22, Temperature = 25- 30C, shelf life =18 months

      You do not want the user to enter this information its a spec that you are controlling and issuing to a Supplier. They are making your product and you are providing the standards.

      Your Sales people may be checking on a product or a customer may request a specification for apple juice then you would access this information

      In the big scheme of things the database manages vendors , who they are , what they produce, product specifications, etc.

      Comment


      • #4
        Re: How Can I do That

        Here's how I would do it: Products table & spec table. Make each one of your specs a field in the Specs table. Craete a 1:1 set using Products as the parent table.
        Peter
        AlphaBase Solutions, LLC

        Peter@AlphaBaseSolutions.com
        https://www.alphabasesolutions.com


        Comment


        • #5
          Re: How Can I do That

          Thanks.
          Are you suggesting that if I have 100 products I would have a 100 spec tables one per product?

          The product table is easy because each record allows me to add a new product and its still one table but because of the uniqueness of the specifications I would need 100 tables. Seems like a lot of work

          Comment


          • #6
            Re: How Can I do That

            Originally posted by clemkonan View Post
            Thanks.
            Are you suggesting that if I have 100 products I would have a 100 spec tables one per product?
            Not at all. Just one spec table. Let's say that you have 100 different specifications in total for all of the various products. Make each spec be a field in your spec table. So now your Spec table ends up w. a 100 or so fields. Each product may only use a few of the spec fields, but they are all in each record; it's just that each spec record may have a lot of blank values for each related product.
            Peter
            AlphaBase Solutions, LLC

            Peter@AlphaBaseSolutions.com
            https://www.alphabasesolutions.com


            Comment


            • #7
              Re: How Can I do That

              Originally posted by Peter.Greulich View Post
              Not at all. Just one spec table. Let's say that you have 100 different specifications in total for all of the various products. Make each spec be a field in your spec table. So now your Spec table ends up w. a 100 or so fields. Each product may only use a few of the spec fields, but they are all in each record; it's just that each spec record may have a lot of blank values for each related product.
              Thanks I get it , I will try it out.

              Comment

              Working...
              X