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

Design considerations help

  • Filter
  • Time
  • Show
Clear All
new posts

  • Design considerations help

    In reviewing Alphasports I noticed that the extension price was a field in the table rather than a calculated field on a form. Up to now, I have thought that the calculated field for a form or a report was the prefered design. It saves a little in storage. Anybody have any strong views?

    Also, I note a similar situation with the "ship to" check box. I don't readily see the design purpose and it doesn't seem to be used to speed up data entry.

    On the "ship to" issue the design requirements have to cover various real requirements (at least for my business).
    1. Ship to customers address (ie bill to and ship to the same)
    2. Ship to address is different from bill to address.
    3. Customer has more than one ship to address.
    4. Customer wants it drop shipping to a third party.
    5. Customer wants it drop shipping to a third party who is another of my customers.

    From the above, my inclination is not to have shipto and billto fields in the customer table but to add each seperate address to the customer table and use a memo field to indicate which of the conditions 2-4 the entry is for, when it is not 1 or 5.

    The invoice has a shipto field which is populated by the appropriate customer id field, with the default value set to that of condition 1 above.

    Currently, the above requirements are only implemented in Alpha Four but as I struggle to move to A5 I was wondering if I need to make any changes in the design to the tables.


  • #2
    RE: Design considerations help


    " I was wondering if I need to make any changes in the design to the tables."

    The answer is yes. Alpha Sports is only a guide to be learnt from. It is not the whole of what Alpha can do. The hard part about Alpha is stretching your imagination into all the things Alpha can do. I am still learning and enjoying every moment.

    Keith Hubert
    Keith Hubert
    Alpha Guild Member
    KHDB Management Systems
    Skype = keith.hubert

    For your day-to-day Needs, you Need an Alpha Database!


    • #3
      RE: Design considerations help

      Hi All,

      I prefer the "bill to" and "ship to" to be separate tables.


      • #4
        RE: Design considerations help

        Steve, when you can have a 60GB hard drive, a few extra bytes doesn't amount to a hill of beans. As for the ship to address, bill to address - there is no DATABASE POLICE! Do it the easiest way always remember KISS (Keep it simple stupid). Then it's easy to modify if required.



        • #5
          RE: Design considerations help

          Incidently, I would definitely NOT consider using a memo field for the addresses.



          • #6
            RE: Design considerations help


            The memo field would not have the addresses. It would say something like -" Smith's customer. See invoice # 4678".
            In looking down my customer lists I need to know my customers and if there is a name I don't recognize then the note is a help. It is impossible to provide all fields in a customer table to keep track of all the data on a customer. A memo field covers these shortfalls.



            • #7
              RE: Design considerations help

              The above is a very common use of memo field.


              • #8
                RE: Design considerations help

                In reviewing Alphasports I noticed that the extension price was a field in the table rather than a calculated field on a form. Up to now, I have thought that the calculated field for a form or a report was the prefered design. It saves a little in storage. Anybody have any strong views?

                If the data is "dead", that is, a record of something, like the amount paid, make it a field.

                If the data is "live", that is, it is meant to reflect a process that may change, make it calculated.

                Invoice info is typically "dead".

                For example, the sales tax in your state may currently be 6%. When you issue an invoice, you want the tax at that moment. When the tax goes up to 6.5% next year, you don't want old invoices showing different values.