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

Task Management

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

    Task Management

    I have two tables.
    Table_One = "Equipment Category Table"
    Table_Two = "Task List"
    '---
    ? Table_One.table_fields()
    = "Equipment_Type"
    "Equipment_System"
    Equipment_Sub_System"

    Equipment_Type would be anything from "Car" to "Chassis" to "Plane" not sure.
    I'm using "chassis" because that's my industry.

    Define all Categories of an "Equipment_Type". They go under "Equipment_System".

    (E.G.)
    Car / Engine, Car / Transmission, Car / Electrical System
    Then Define the Specific Sub Systems (a.k.a. Parts)
    Car/Engine/Intake
    Car/Engine/Sensors
    Car/Electrical System/Harness
    Car/Electrical System/Alternator

    Give every Combination a unique serialized number called "Category_ID"
    This "Category_ID" is used to Link "Maintenance Tasks" to a specific area of a defined Equipment.

    ? "Table_Two.fields_get()
    = Category_ID
    Component
    Action
    Time Allowed
    Usage Limit
    Specifications

    Every "Task" is linked to a "Category_ID" on an equipment. Progressive Search through the categories, and find your Component. The Component will be used to show all possible Actions. When a component and an action are chosen, this record can be given a unique serialized "Task_ID".

    This "Task_ID" is placed onto a "Work Order" table. The "Task_ID" has a limit to how many of them is allowed on a "Work Order". Each "Task_ID" has a Time Allowed assigned to it, and also a Specification field which details the limitations and instructions of a "Task".

    This is my method of using "Tasks" for a CMMS. Every "Task" is basically an Action done to a "Component" which is located in the "Category_ID" of an "Equipment_Type".

    Logically I think this may work well, but there are still things I'm missing that I'm not aware of. I also use this "Category_ID" table to define "Parts". I do not add "Parts" to a "Work Order" using a Progressive Search, instead I simply search for a "Part_No" or "Description". I say this because my "Parts" sometimes need a "Category_ID" of their own. Those Categories exist that do not have any "Tasks". This isn't a problem I think, because when Searching for a Task you would just know which Categories will have Components and Actions (A.k.A "Tasks"). That is a problem because I want the User to See Exactly what he needs to see and nothing else. Clicky Clicky Boom Boom.

    My brain hurts. Can anyone help me figure out this system. I need someone with a brain and some creativity. I know all of you do this for a living. :) Really it doesn't seem too complicated or difficult, but it is. Especially the "Idiot" factor which requires me to have everything "editable".

    Please and thank you for any suggestions or comments...
    Dan Murphy

    #2
    Re: Task Management

    I can see why your brain hurts, but at the same time you seem to have a fairly intuitive, if not nuts & bolts, grasp of what you are trying to do. A couple of points, though:

    When you say: Car/Engine/Intake, etc. to me that suggests 3 tables, not one. But I may be wrong. As a general rule, you should follow the rules of db normalization - i.e. break your db structure up into the smallest parts possible, each "part" being a table. Each record of each table (in most cases) should have their own unique (autoincrement) ID. Then link as need be.
    Peter
    AlphaBase Solutions, LLC

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


    Comment


      #3
      Re: Task Management

      Hi Daniel

      Logically I think this may work well, but there are still things I'm missing that I'm not aware of. I also use this "Category_ID" table to define "Parts". I do not add "Parts" to a "Work Order" using a Progressive Search, instead I simply search for a "Part_No" or "Description". I say this because my "Parts" sometimes need a "Category_ID" of their own. Those Categories exist that do not have any "Tasks". This isn't a problem I think, because when Searching for a Task you would just know which Categories will have Components and Actions (A.k.A "Tasks"). That is a problem because I want the User to See Exactly what he needs to see and nothing else. Clicky Clicky Boom Boom.

      not sure but i am thinking that you need a field(CLASS) that might be used to filter
      the tasked parts from the non tasked parts - if you keep them all in the same table.

      this would allow the use of "Category_ID" for both types of parts searches if you set the filter for the CLASS search to "A" - ancillary or "P" primary

      just a thought
      regards

      martin
      www.jollygreenthumb.com

      Comment


        #4
        Re: Task Management

        Brilliant, two great responses. :) Yes the Class idea would work, have two three possible values.
        "Part"
        "Task"
        "Both"

        Nice. Thanks. Actually Peter I have all three "Category" fields in one table and each record has a unique "Category_ID". In reverse, every "Category_ID" has three distinctive location markers. You might be right about splitting them up into a Type table, System Table, and Sub_System Table. Then creating unique IDs to link together every possibly combination...However, at this point I might want to table.external_record_content_get() for a progressive search in a dialog filtering through the same "Master Category" table. When the three descriptions are chosen, that "Category_ID" can link to anything. At least this isn't as far fetched as I imagined it would be.

        All in all it's a solid foundation to do what I'm doing? :)

        Thank you all

        Comment

        Working...
        X