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

structuring my database and linking tables

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

  • DaveM
    replied
    Re: structuring my database and linking tables

    I did this one years ago. Keith's way is one way. I made the invoice table with fields for 2 service writers, 2 in the office and 4 tech's because of 1 for body, 1 for paint, 1 for finishing, 1 for cleaning(maybe a couple of spares). You don't always use all, but they are handy to have. each of the above fields were lookups to 1 table for employees that had a code for their job function. That code was used to filter the lookup. I had a couple other tables too, but don't remember all of them. This all tied into the payroll(seperate app). The inv also was used by mechanical repair and sales.

    invo = invoice
    empl = employee

    (I like short names)

    Leave a comment:


  • Keith Hubert
    replied
    Re: structuring my database and linking tables

    You need a Header table for the Service Order with lookup fields to table where single data is required and child tables for multiple records. So, as you want more than one technician to service then you will need to have a child table linked 1:N with a lookup field to the technician's table. In each of these records you would also keep the time that the "technician" starts and stops servicing the unit.

    Have a look at AlphaSports Invoice form. It might take a little imagination to apply to your situation but the answer is there.
    Last edited by Keith Hubert; 02-02-2012, 02:52 AM.

    Leave a comment:


  • paintacar
    started a topic structuring my database and linking tables

    structuring my database and linking tables

    Sorry I am learning how to set up my tables. I have a question about how I should configure my tables. Lets say I have a table for employees and it includes office staff and technicians with ID number for each, so really it has fields basicly to store their names and direct phone lines for office staff along with the employee's ID number. Then I have a table with repair order number and item being serviced along with who is the office staff that is assigned and who the technician is servicing the unit and the status of service and the date the unit went into service and the date it is scheduled to be out of service. Since each unit can have more than one technician assigned to it and each technician and/or member of office staff can have more than one unit assigned to them, should I have one table for office staff and one table for technicians and one table for service status and one table for service dates? I originally thought I could have an employee table to hold contact information and names and enter the names under "office staff" or "technicians" depending on their position. and just use that table to supply the dropdown list to enter the "office staff" and "technician" fields in the main repair order table and also store the date information in the repair order table as well. If I seperate the tables wouldn't it still have to have a field in there to say the same thing ? or at least provide the same information that I was going to store there anyways? I had also planned on storing the time that the "technician" starts and stops servicing the unit. should I store that in a seperate table as well? or in the same table? because it is specific to that specific repair order? and if I am to store it in a seperate table then how do I join it? Suggestions are greatly appreciated.
Working...
X