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

What first step do you take when building tables from scratch?

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

  • What first step do you take when building tables from scratch?

    I've seen the videos on repeating sections that show how to build parent-child dependencies through the Data Binding section table builder. In a different thread it was suggested that using MySQl or similar programs is easier/better. First to build out a schema there, and then build a connection string to the data.

    From my current viewpoint, both seem quite challenging since there's very little documentation on how best to approach building the relations between tables on the backend of this program. Almost every video starts by importing the Northwind db and then creating "flat" grids or list controls that don't address relations between tables.

    This question is to more developers with more experience under their belts. What approach are you using when starting out in AA?

    Regards,
    Richard

  • #2
    Re: What first step do you take when building tables from scratch?

    Data design drives everything... you always start there first... with a SQL backend (MySQL, SQL Server, MariaDB, etc) it doesn't matter which. Start building out your parent table first, then the child tables.

    Northwind still offers a good example with the Customers, Orders, Order Details tables.

    You're not building "the backend of this program", you're building a good, hierarchical back end. It's got nothing to do with Alpha or any other front end... it's just a good data design.

    Then, when you start building in Alpha you'll see how easy the data fits into the tools. Parent data with Child data Repeating Sections, Parent-Child Lists... it's all the same pattern.

    Comment


    • #3
      Re: What first step do you take when building tables from scratch?

      You will not regret taking a step back and following David's advice. For someone who has used excel SQL is not too different visually. The data resides in tables. Excel calls these sheets.

      Often people attempt to use a "Flat" structure in excel and this is not encouraged in SQL. Look at Northwinds as David suggested. Try to understand the idea of splitting the "Flat" data that excel may display in one sheet, as 3 linked tables. An order detail is linked by a "Key" to an order which in turn links to a customer. The idea is if you know the order detail then you can find your way back to the customer.

      Having said all of that if you want to play on your own then Alpha has a way of building tables for you.

      Message answer..png

      Good luck

      Comment


      • #4
        Re: What first step do you take when building tables from scratch?

        in order to learn basics of database design, which is what i deduce from your question, there are lots of material out there on the internet, better yet books on database design. a better database design will help you achieve your final end better.
        a better database design starts with what you want in the end, the outcome. then you design the beginning, the end dictates the start. before a single keyboard click to start designing, always write down what you want then see if you can separate the data into smaller pieces so there is less repetition of data. then only design in the database software. alpha sql design is fairly easy but as far as i know it does not give you flexibility as you would get by yourself like designing in phpadmin, navicat or toad.
        reading, studying northwind database is good, if you already know how to design the tables and their structures, since it is a finished product, in order to take you thru building and teach design basics you need to read database design books or internet. even then the concept will be adjusted as time goes on and as you mature in database design. once you learn the basics then nothwind will definitely help you fine tune your idea.
        in any case good luck and have fun.
        thanks for reading

        gandhi

        version 11 3381 - 4096
        mysql backend
        http://www.alphawebprogramming.blogspot.com
        ggandhi344@gmail.com
        Skype:ggandhi344@gmail.com
        1 914 924 5171

        Comment


        • #5
          Re: What first step do you take when building tables from scratch?

          Hello,

          Start up with the database design is crucial for any application development. We are using xCase as data modelling tool. Have a look at this article: Reverse Database Engineering and Database Design.

          That tool will help you to design your database and will generate the script for any table, indexes, relations and more without leaving this tool at all.

          Regards,

          Doron
          The Farber Consulting Group, Inc.

          Main Web Site: http://www.dFarber.com

          Avis Car Rental Software
          MS SQL Blog: http://http://www.dfarber.com/computer-consulting-blog/
          Convert Ms Access to Web
          Last edited by Steve Wood; 08-17-2017, 12:37 PM. Reason: fixed hyperlink

          Comment


          • #6
            Re: What first step do you take when building tables from scratch?

            Thanks, I appreciate it.

            Comment


            • #7
              Re: What first step do you take when building tables from scratch?

              where can I download this application "Reverse Database Engineering and Database Design".
              I like to try it.

              Comment


              • #8
                Reverse database Engineering

                Hello Wale,

                Check this company named xCase.

                Regards,

                Doron
                The Farber Consulting Group, Inc.

                Main Web Site: http://www.dFarber.com
                Alpha AnyWhere Development
                Reverse Database Engineering and Database Design

                Comment


                • #9
                  Re: What first step do you take when building tables from scratch?

                  one thing to consider in design is to count on user tracking and data manipulation tracking, which I wish I had done from the beginning. Take, for example, the deletion of an invoice. What if the user of your app wants to "undo" that? What if there are two logins for the same account and one of them makes an update to a record and the other calls you to say his data changed? The idea would be that you could then look into it and say well there was a login at 2:45pm by user1 who updated that record.

                  I would say though that just starting out you will want to flesh out the amount of redundancy you want in the data that you want to track and as others have said it really depends on you and what data you want to store. For me, event tracking has been something I added later as the need surfaced but I wish I had it in place from the beginning as part of the base table design.
                  NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                  Comment


                  • #10
                    Re: What first step do you take when building tables from scratch?

                    Time stamps are something I've been trying to get my head around. So I created 6 tables: User entered data(id field), user changed data(id), date entered(date), date changed(date), time entered(time_stamp), time changed(time_stamp). I've followed different Javasript examples and not working so far. Of course I'm not sure where JS should be placed. I just copied some stuff from this forum, and not much else.

                    Comment


                    • #11
                      Re: What first step do you take when building tables from scratch?

                      You should let your SQL Tables handle this... and just have 1 dateCreated and 1 dateUpdated field. Each field type is datetime. You don't need separate date and time fields.

                      The dateCreated field will have the default value set to CURRENT_TIMESTAMP.
                      The dateUpdated field will have the option On Update CURRENT_TIMESTAMP turned on.

                      timeStamp1.PNGtimeStamp2.PNG
                      Last edited by Davidk; 08-22-2017, 09:01 PM.

                      Comment


                      • #12
                        Re: What first step do you take when building tables from scratch?

                        Hi Rich,

                        Time stamp you use when the record is saved. In MS SQL the function for that is GETDATE() and you use that as default so all is done in the database level without even thinking about that. No need to use JS for that.

                        Regards,

                        Doron
                        The Farber Consulting Group, Inc.

                        Main Web Site: http://www.dFarber.com

                        Avis Car Rental Software
                        Custom Software Development
                        Last edited by DoronF; 08-23-2017, 12:15 PM.

                        Comment


                        • #13
                          Re: What first step do you take when building tables from scratch?

                          Thanks David and Doron. I wasted a lot of time trying it client side when it's server side stuff.

                          In MySQL the time stamp is expression CURRENT_TIMESTAMP, and it autosaves date and time. Works like a charm!

                          Comment


                          • #14
                            Re: What first step do you take when building tables from scratch?

                            Thanks Charles, for sharing such a great ideas…..!

                            Comment


                            • #15
                              Re: What first step do you take when building tables from scratch?

                              This forum led me to this book, and I can't recommend it enough.


                              database_design_for_mere_mortals_3rd_edition_j_hernandez(www.ebook-dl.com)_Large.jpg

                              Comment

                              Working...
                              X