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

Too many links in a set

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

    Too many links in a set

    Hello,
    There must be a better way to do this.
    I have a form that shows "employee#" and I would like to bring in the "employee name" from the employee table (the main table only contains codes).
    Without doing 60 links in the set, how can I set it up so when an employee# is selected from a drop down box, the employee name is presented on the screen too?
    Thanks.

    #2
    RE: Too many links in a set

    Don't understand the "60 links". You only need to link the main table to the employee table once based on employee id (I assume that's the field in both tables) and show the employee table employee name on the form.

    IOW the main table should have employee ids and the employee table should have employee id, employee name, and other employee data.
    There can be only one.

    Comment


      #3
      RE: Too many links in a set

      I'm sorry I should have been a little more specific. There are approx. 60 unique fields (job positions)with employee# as the field value. I would like to be able to allow the input person to select from a list for each of the unique job position fields and display the employee name on the form.
      My thought was I would have to do a link for emp_code (JobPosition1) to the emp_code in the Employee table for each of the unique JobPositions(1-60).

      Comment


        #4
        RE: Too many links in a set

        Ahhhh, another spreadsheet guy appears!

        Daniel, databases work best if information is organized differently than you describe. Instead of sixty fields each of which will hold a single value, you will be far better off with a single field that can hold any of sixty different values.

        -- tom

        Comment


          #5
          RE: Too many links in a set

          Is this for a business with 60 positions which are relatively static, or are you creating personnel lists for jobs, each of which has 60 positions which are filled from a central employee table?

          In the first case (static employee list), I would use three tables:

          parent - your main table, with fields for position code and employee code. Perhaps also date filled, other info relative to the hiring.

          child table 1, linked one to one by position code - positions, each record containing a position code, position title, other info about the position.

          child table 2, linked one to one by employee number - employees, each record containing an employee code, name, etc.

          In the second case (multiple jobs), four tables:

          parent - jobs, with each record containing info about a specific job, including a job code.

          child, linked one to many by job code - a linking table, containing all the same info as the parent from the first case above plus a field for job code.

          grandchild 1, linked one to one - positions, see child table 1 above.

          grandchild 2, linked one to one - employees, see child table 2 above.

          With this setup, you can use a form with an embedded browse or a report to show who fills each position for a given job. Or, by creating other set configurations using the same tables, you could get a list of all the jobs an employee has worked, all the different positions an employee has filled, all the employees who have filled a particular position at some time, etc.

          Good luck!

          Sherrill

          Comment


            #6
            RE: Too many links in a set

            Wow! What a dynamic forum!!! We are truly very lucky to have such a "sounding board"!
            Basically what I am doing is creating a rough schedule for employees each with a different role. The input process is pretty sound. A table has been created containing fields for the unique job positions which reference an employee master to get employee data.
            My problem is for viewing purposes, I would like to show the name of each employee for each of the job positions. On a smaller scale I have accomplished this by creating multiple links within the set and physically dragging/dropping the name from link1, link2, link3... to the appropriate positions on the form.
            There must be something I am missing here. Does a table link need to occur for each job position when the key will always be the same - empl#? Again, this is just for display purposes.

            Comment


              #7
              RE: Too many links in a set

              Daniel,

              I would like to show the name of each employee for each of the job positions.

              Make a set as follows:

              Parent Table - Job Positions
              Child Table - Employee's Linked as 1 to many, Linking field "Position_No"

              If an employee holds mutiple positions then create a new table structured with the following fields:

              Job_No, Position_No, Employee_No

              Now replace the child table with this one with the same links.

              An easy way to think of this is to use a Invoice type structure where instead of Invoice_header as the parent table you have Postions. Instead of the invoice_line_items you have either employee or jobs.

              Hope this helps you,

              Scott

              Comment


                #8
                RE: Too many links in a set

                Although I agree that there might be better ways to design tables to accomplish your goal, you might want to investigate the following function:

                LOOKUPC(

                as a way of retrieving the name of an employee with a known employee ID.

                Comment

                Working...
                X