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 to construct Northwind table set in A5?

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

  • How to construct Northwind table set in A5?

    I thought I understood how to do this until I acutually tried to do it today. In A5 table designer, how would I construct the following table set (just focusing on the blue tables for now)?

    Northwind Entity-Relationship Diagram

    My initial impulse is to designate the 'Orders' table as the primary table. From there I would construct a Many-to-One link to the 'Customers' table. Finally, I would construct another Many-to-One link to the 'Employees' table. However, A5 appears to allow only One-to-Many and One-to-One links. It does not appear to allow Many-to-One links. I suspect that I am misunderstanding a fairly fundamental aspect of A5 use or DB design. If I can get off the starting block here, I think I will be able to make some decent progress. Any help would be appreciated. Thanks.

    Jim

  • #2
    Re: How to construct Northwind table set in A5?

    how would I construct the following table set
    Perhaps you don't need to? Alpha has tools to look up the employee details based on the employee id. It doesn't need to be part of the set.
    There can be only one.

    Comment


    • #3
      Re: How to construct Northwind table set in A5?

      In addition to what Stan said...

      My initial impulse is to designate the 'Orders' table as the primary table. From there I would construct a Many-to-One link to the 'Customers' table.


      Since Alpha uses sets, you could create a 1:M set like this:
      Code:
      Customers [1:M] Orders
      But if you need to see orders linked to Customers, then:
      Code:
      Orders [1:1] Customers
      Finally, I would construct another Many-to-One link to the 'Employees' table.

      Similarly:

      Code:
      Orders [1:1] Employees
      and/or

      Code:
      Employees [1:M] Orders
      and/or

      Code:
      Customers [1:M] Orders [1:1] Employees
      or

      Code:
      Orders [1:1] Customers 
             [1:1] Employees
      etc etc
      Peter
      AlphaBase Solutions, LLC

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


      Comment


      • #4
        Re: How to construct Northwind table set in A5?

        Originally posted by Peter.Greulich View Post
        In addition to what Stan said...]

        Since Alpha uses sets, you could create a 1:M set like this:
        Code:
        Customers [1:M] Orders
        But if you need to see orders linked to Customers, then:
        Code:
        Orders [1:1] Customers
        Finally, I would construct another Many-to-One link to the 'Employees' table.

        Similarly:

        Code:
        Orders [1:1] Employees
        and/or

        Code:
        Employees [1:M] Orders
        and/or

        Code:
        Customers [1:M] Orders [1:1] Employees
        or

        Code:
        Orders [1:1] Customers 
               [1:1] Employees
        etc etc
        Peter,

        Thanks for your response. I am not sure I understand it, but you have given me something to chew on. Let me see if I can restate, in part, what you are telling me.

        Are you saying that my desired set, Employees[1:M]Orders[M:1]Customers ...the structure shown in the Northwind ERD,
        is functionally equivalent to, Customers[1:M]Orders[1:1]Employees[1:M]Orders? Is this a 'work-around' structure in A5 that you are suggesting; the 'work-around' being necessary since A5 does not allow overt [M:1] table links? Am I following you? With this structure, wouldn't the database engine be more confused than I am? :) Seriously, in addition to the expected Orders[M:1]Employees link, this structure includes an Orders[1:1]Employees link as well. Is that not ambiguous? Is that not problematic?


        Thanks,

        Jim

        Comment


        • #5
          Re: How to construct Northwind table set in A5?

          Originally posted by Peter.Greulich View Post
          In addition to what Stan said...]

          Since Alpha uses sets, you could create a 1:M set like this:
          Code:
          Customers [1:M] Orders
          But if you need to see orders linked to Customers, then:
          Code:
          Orders [1:1] Customers
          Finally, I would construct another Many-to-One link to the 'Employees' table.

          Similarly:

          Code:
          Orders [1:1] Employees
          and/or

          Code:
          Employees [1:M] Orders
          and/or

          Code:
          Customers [1:M] Orders [1:1] Employees
          or

          Code:
          Orders [1:1] Customers 
                 [1:1] Employees
          etc etc
          Peter,

          Thanks for your response. I am not sure I understand it, but you have given me something to chew on. Let me see if I can restate, in part, what you are telling me.

          Are you saying that my desired set, Employees[1:M]Orders[M:1]Customers ...the structure shown in the Northwind ERD,
          is functionally equivalent to, Customers[1:M]Orders[1:1]Employees[1:M]Orders? Is this a 'work-around' structure in A5 that you are suggesting; the 'work-around' being necessary since A5 does not allow overt [M:1] table links? Am I following you? With this structure, wouldn't the database engine be more confused than I am? :) Seriously, in addition to the expected Orders[M:1]Employees link, this structure includes an Orders[1:1]Employees link as well. Is that not ambiguous? Is that not problematic?


          Thanks,

          Jim

          Comment


          • #6
            Re: How to construct Northwind table set in A5?

            Originally posted by drjgs200 View Post
            Is that not ambiguous? Is that not problematic?
            Not really. Alpha uses an alias on the 2nd instance of the Orders table.
            Peter
            AlphaBase Solutions, LLC

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


            Comment


            • #7
              Re: How to construct Northwind table set in A5?

              Thanks again, Peter. I will try your suggestions.

              Jim

              Comment


              • #8
                Re: How to construct Northwind table set in A5?

                Hi Jim
                Don't confuse the entity relationship diagram with sets. A diagram would likely use multiple sets for different purposes.
                As Peter's examples indicate;-
                First determine what your focus is centered on for a particular task or query and design a set for that - there is need only for 1-1 or 1-many.

                Comment

                Working...
                X