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



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

Layout Help?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Layout Help?

    I'm new to best practices and using an actual data layout, so would appreciate if you see anything I can improve with this simple MySQL layout.

    System will run my startup company that I hope will grow large, so want to get as right as possible out of the gate. One DB would auto-dispatch as many as 10K techs nationwide, some 10K new records and 50K web accesses daily. (I figure if Allpha doesn't scale there now, it will with IIS.) It would also auto-notify and auto-bill clients and manage marketing contacts.

    Regions segment the data into several groups, but system will also use geo-radiuses, so regions would cut a little overhead.

    Any ideas at all? I welcome criticism.
    Attached Files
    Last edited by jchasko; 08-30-2011, 06:20 PM. Reason: Updated Layout

  • #2
    Re: Layout Help?

    If you built the Schema with Toad for MySql it will validate it for you.
    Personally I'd split the Employee table and have the Manager bit separated out.
    Suggest you build it in Alpha using Sets to prove the concept, and then create the SQL tables from there.
    Integer or Char. There has been a bit of debate around this recently. Your choice for whichever is most easily understood and maintainable.
    Normalisation. Unless you are a purist and enjoy the challenge which mere mortals (who have to maintain such apps) aspire to, keep it simple. A bit of redundant data isn't as bad as the old days of disk storage.
    See our Hybrid Option here;


    • #3
      Re: Layout Help?

      Thanks. I have since laid it out in MySQL. I moved away from a universal lookup table. It just obscures the function, which is the opposite of maintainability.

      Can you help me with "Sets"? I don't see it in Alpha 5, it does not come up in the Wiki Page Search. But nothing ever does for me.

      I'm interested in your suggestion on Employee. Would you put the commission rates into a table, with the two types (tech and mgr) as rows for each employee? Put the period figures into a third employee table?
      Last edited by jchasko; 08-30-2011, 10:29 AM.


      • #4
        Re: Layout Help?

        Sets. Look in the Help Documentation first.
        Wiki. Look at the threads in "How to use the Forum" section. Comments in there regarding AlphaWiki and searches.
        Employee table change = Yes. But it's your trainset so this would be my way of working.
        See our Hybrid Option here;


        • #5
          Re: Layout Help?

          If it were a feature/module, it ought to pop up under Title Search or Title Search ought not to exist. I know how to full-text search. But "sets" is a highly non-unique term.

          What is Sets?


          • #6
            Re: Layout Help?

            Good suggestion. I've been working on the MySQL layout for a few days, including your excellent advice on Employee. I pulled employee type and commission rates out, added commission history. Similarly, where I was putting business logic into the structure of the service order (old, old bad habit), I pulled info into small tables. Added company/unit, with issues, based on problem type and severity, and which link to service orders. Simple and obvious.

            Much better. The beauty of it is that you can see the business logic visually in the model. Wow. I guess that's Duh to you guys, but new to me. Very cool.

            A universal lookup table is not a very useful idea when the individual lookkups document your logic!