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

Table Design for Contacts

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

    Table Design for Contacts

    Hello all,

    I have a newbie question regarding how to design my contact tables. The idea is that I have one contact tabe with standard info (name, number, adress etc) and that I have additional info attached to the contact depending on what the contact�s role is.

    Example:

    Table 1 = Contact info / PK = ContactID
    Table 2 = Employee info / PK = ContactID
    Table 3 = SalesEmployee info / PK = ContactID
    Table 4 = Client Info / PK = ContactID
    etc etc

    The idea is that I should have only one table with basic contact info so I only have one table to search in and only one table to add ulilnk info to.

    So how do I solve the problems that amployees should only have access to search other emplyees contact info, sales should only be able to search Clients etc etc etc. My problem is that all contacts is in the same database, but users should only be able to search contacts depending on what other tables are connected to them.

    Does it make sense? Maybe I should solve i in a better way?

    Thanks for any help, I am quite new to this...

    Robert

    #2
    Re: Table Design for Contacts

    Does it make sense?

    Hhhmmm, maybe? You might consider using only one table with a field identifying what type they are - Employee,SalesEmployee,Client, etc. Use that "type" field as a filter on your grid(s). Search through the video archive to see how to pass a filter to a grid.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: Table Design for Contacts

      Is this information actual "Contacts" or System Users?
      _______________________________
      Steven McLean
      i3 Home Inspections
      [email protected]

      Comment


        #4
        Re: Table Design for Contacts

        Originally posted by StevenMcLean View Post
        Is this information actual "Contacts" or System Users?
        I am thinking of every contact, independent of what kind of contact it is.

        I still don't know if it is a good idea, but I have been speaking to a more professional friend of mine and he said it is not such a bad idea.

        What I gain:
        I have a nice contact list with every contact in the system, independent of the role.
        Any contact can be a DB user, because every contact has a unique contact ID in the same table, doesn't matter if it is a client or an employee or whatever else that might come up.

        What might be bad:
        If I want someone to only see clients, they will have to look in the "client" table and get the contact info backwards by looking 'up' in the contact table. But according to my knowledgeable friend it should not matter(?).

        Thanks for taking interest!
        Robert

        Comment


          #5
          Re: Table Design for Contacts

          If every contact could be a db user, you will need to design your security system around that paradigm with levels of access restrictions to set which db user / contact can see. Depending on your industry and type of data you store dictates if it is an issue if users see more than they should.
          _______________________________
          Steven McLean
          i3 Home Inspections
          [email protected]

          Comment


            #6
            Re: Table Design for Contacts

            Originally posted by StevenMcLean View Post
            If every contact could be a db user, you will need to design your security system around that paradigm with levels of access restrictions to set which db user / contact can see. Depending on your industry and type of data you store dictates if it is an issue if users see more than they should.
            Thanks for your thoughts.

            Yes, I am planning to have a few groups which should more or less match the subtables. So the "clients" will have a subtable with specific info and its own usergroup for security reasons.

            Robert

            Comment

            Working...
            X