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

Many to Many DBF

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

    Many to Many DBF

    I am having a conceptual problem creating a database. I have a list of servers and a list of software applications. I want to have one screen showing each server that has a browse in it showing the apps running on it. I also want to have one screen showing each app that has a browse in it showing each server.

    I've gone round and round this, but can't seem to find the answer. Is there one? Please help!

    Charlie

    #2
    RE: Many to Many DBF

    Charlie:
    this might not b the best way but I think I would create
    2 operations to summarize the tables.
    summarize application to application and server
    and summarize server to aerver and application

    then you would have 1 record in each table the way you wanted to see it.
    then you could just view the files in a report or a form browse.
    this might not b the best , but it is easy to do

    yu could also yse sets to view the info.
    Charlie Crimmel

    Comment


      #3
      RE: Many to Many DBF

      Charlie, it sounds like two tables, and two sets to me.

      In the first set, each server is linked one to many to the apps. Link field is the server name.

      In the second, each app is linked one to many to the servers... and the parent table's current index is set to unique values. Link field is the app name.

      Within the apps table you will have to include a field to identify a server,
      and within the servers table you will have to include a field to identify an app.

      Xbasic scripts could be used to update the second table, whenever a change is made to the first.

      I confess to never having built anything quite like this, so take my comments with a large ration of salt! (...often wrong, but never in doubt!) -- tom

      Comment


        #4
        RE: Many to Many DBF

        A good example of this is the Employee example that ships with A5.
        There is a set consisting of Employees and training classes. In one view you can see an employee and all the classes for the employee. In another view you can click on a class title and see all the employees that have taken that class.

        Dan
        Dan

        Dan Blank builds Databases
        Skype: danblank

        Comment


          #5
          RE: Many to Many DBF

          What about 1 set as follows...

          Servers
          =======>Apps (child of Servers)
          ===========>Servers(Child of Apps)

          Servers is Parent with Apps linked to it 1-many, then with Servers then linked to Apps 1-many. Servers would be grandchild of itself.

          Visualize one form with 3 browses. 1st browse is Servers, 2nd is Apps, 3rd would then be Server that is linked 1-many to Apps.

          1st browse you can see all your servers. Whichever line is highlighted will display all Apps on Server in browse 2. Say 3rd line in 1st browse is for Server C. 2nd browse would display all Apps running on it. Then go to 2nd browse that's displaying all Apps running on Server C. As you scroll through the record in browse 2, browse 3 will display all servers that each App is running on.

          Does all this nonsense make anysense to anyone?

          Seems to me that you'll be able to see everything that you want right on one screen, if that is your ultimate purpose.

          Let me know what you think?

          Mike
          Thank you,
          Mike Konoff

          Comment


            #6
            RE: Many to Many DBF

            All many to many relations normalize to multiple one to many relations. The example everyone knows is students to classes which is N:N since each class has many students and each student enrolls in multiple classes.

            This normalizes to two 1:N relations:
            Students to classes (known as a student transcript)
            and
            Classes to students (known as a class list)

            I thought I would add this example as it is so clear.

            Bill
            Bill Hanigsberg

            Comment


              #7
              RE: Many to Many DBF

              In any Many to Many relationship you must be careful in the link settings. Referential Integrity must be off for any links to the child records of the 1 to many. Also changing (and probably adding) child records must also be disabled.
              The reason for this is that having this feature on, it locks the children while the parent is in change mode. Another parent record that uses 1 or more of those children will not be able to go into change mode until the children are unlocked (by doing a save).

              With the feature off, any changes to the child records should be done in a table or set using the children as the parent (normally by opening a form based on the needed record). This will only lock the record being edited.

              Referential integrity needs to be coded as a indivisible operation that occurs at save time.

              Regards,

              Ira J. Perlow
              Computer Systems Design & Associates
              [email protected]
              Regards,

              Ira J. Perlow
              Computer Systems Design


              CSDA A5 Products
              New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
              CSDA Barcode Functions

              CSDA Code Utility
              CSDA Screen Capture


              Comment

              Working...
              X