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

A memo field to carry a table

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

  • A memo field to carry a table

    In my database I have tables for vendors and products ,etc. ProdID is a primary key and will allow me to display:

    1) prodID - which is the UPC
    2) Common Name - for example 2% Milk
    3) Size - for example 2Litre

    But I also want to have the specification for this product, for example:

    1) Shelf life -30 days
    2) Coding format
    3) code Type
    4) code placement
    5) Declared fill
    6) total bacterial count
    7) % butter fat

    Should these quality factors come from a table(s) or can I use a memo field and use a formatted table and if so can I se a quick example of how this could be done.


    Thanks again

  • #2
    Re: A memo field to carry a table

    Originally posted by clemkonan View Post
    can I use a memo field and use a formatted table
    ? sorry, don't understand the question.
    Peter
    AlphaBase Solutions, LLC

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


    Comment


    • #3
      Re: A memo field to carry a table

      Clem, if the additional specifications will apply to most all your products, then putting each into a separate field makes sense. They will be more accessible there than if you string them together in a block of text you store in a memo field. On the other hand, if each product will have different specification categories, perhaps a block of text in a memo field would be better.

      Comment


      • #4
        Re: A memo field to carry a table

        I was basically asking if generating a specification for different categories of products is best handled by creating a table say tblproductspec ( % Fat, Declared fill, Colour, Taste , bacterial count) or if a memo field in the tblproducts woulld suffice.
        I will have about 60 products but these will fall nicely into about 8-10 categories and the specification for a category will be the same with very minor changes for example for whilte milk the fat level ( skim, 1%,2%,3.25%) will vary but everything else is the same.

        Comment


        • #5
          Re: A memo field to carry a table

          Originally posted by clemkonan View Post
          I was basically asking if generating a specification for different categories of products is best handled by creating a table say tblproductspe...c or if a memo field in the tblproducts woulld suffice.
          I still don't understand what you are asking, but I guess Tom does. But answering your question generically, if you need to search, query, retrieve, report, etc. on specs, then put that data into fields. If not, use the memo.
          Peter
          AlphaBase Solutions, LLC

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


          Comment


          • #6
            Re: A memo field to carry a table

            Sorry about that , your last recommndation works for me. I may want to use the spec in a query or to generate a report so I will go with tables , everyone shops so this example should be clear:

            1) tblNFTSpec will carry the nutritional information
            2) tblcaseSpec will carry specifications relavent ot the shipping case
            3) tblretail will carry information specific to the sell unit other than nutritional
            4) tblIngSpec will carry the ingredient listing
            and so on.

            Good job all your responses were very helpful.

            Regards
            Clemkonan

            Comment

            Working...
            X