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

Tips please on how to approach a set/constraint design...

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

    Tips please on how to approach a set/constraint design...

    I'd appreciate some tips on how to design required sets and constraints for an activity signup database (web based).

    Background: The YMCA Adventure Guides allows groups (circles, which in turn are part of larger groups called expeditions )of dads and their kids (people) to get together and do fun things (activities).

    The attached diagram shows the relationships:

    http://home.pacbell.net/eulimi/yag_erd.GIF

    Each person can be a member of one or more circles (each kid belongs to one circle. Each dad can belong to 2 or more cirlces if the dad has more than one kid in the program.) Each circle belongs to one expedition. The administrator associates several allowed activities to each expedition. Each activity could be associated with more than one expedition, hence the activity-exped table. Each person can sign up with one or more activities. Each activity can, of course, be participated in by more than one person, hence the signup table.

    When the user selects a record in the person table, the user can then sign-up the person for one or more activities (in a "child" signup table that appears). My question is: How do I constrain the list of allowed activities for a person based on that person's membership in the expedition? For example, the girls expedition is called Atlantis. The Atlantis record in the expedition table is associated with an activity called the Sweetheart Dance (a Valentines father/daughter event) in the activity table. So, if a person (girl) is a member of a circle that's a member of Atlantis, I'd like the user to be able to sign up the girl (and her dad) for the Sweetheart Dance via the signup table. Boys, on the other hand, are members of the Northstar expedition. Northstar wouldn't, of course, be associated with the Sweetheart Dance. So, if the user is signing up a boy for an activity, the Sweetheart Dance shouldn't appear as an option. (The boy's father could sign up for the dance IF the boy has a sister, who'd be in a girls' circle.)

    I imagine that I'd have to make a multi-level set to impose signup constraint rules, but I'm not sure if this is the best approach. Note that I'd eventually like to present the user with a series of checkboxes next to allowed activities for each person. Check the box to attend, leave unchecked if not attending.

    Thanks very much for your ideas!

    -Kurt

    #2
    Re: Tips please on how to approach a set/constraint design...

    Hi Kurt,

    Just to let you know why you have not had any answers, you have posted your question in the desktop section.

    Try again in the Web Server section of this board.

    Good luck.
    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


      #3
      Re: Tips please on how to approach a set/constraint design...

      Thanks Keith. I'll try the app server section next, although the logic of the problem is the same, I think, as it would be as a multiuser desktop app.

      In any event, Tom Cone just had a crack at my subsequent rewrite/simplification of the problem. Please see thread

      https://forum.alphasoftware.com/showthread.php?t=76598

      Thanks!

      -Kurt

      Comment


        #4
        Re: Tips please on how to approach a set/constraint design...

        Hi Kurt,

        I understand your use of the word Constrain, this is a table rule you can set up in an SQL table. It is not quite the same with a dbf table.

        The question here is, how do you restrict the number of allowed activities for a person based on that person's membership in the expedition.

        The way I would do that is with Flag fields. You would have to work out if they should be counters, logical or both. The Flags could then be set with field rules.

        Hope that helps a bit.
        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


          #5
          Re: Tips please on how to approach a set/constraint design...

          Thanks Keith. I've noted your idea about flags. I'm also posting the question in the app server forum to see what comes up there.

          I've got a feeling this won't be a slam dunk, at least for a newbie like me.

          -Kurt

          Comment

          Working...
          X