Jump to content
  • 0




7 answers to this question

Recommended Posts

  • 0

Hi JckDY,

The first step in creating a web-based application is to build a normalized table. Make sure that the tables are well-architected accordingly to the needs of your application. You can click the links below:
Introduction to Table and Table Design  
Data Normalization: https://www.youtube.com/watch?v=oexOYUUyQik    
One-to-Many Relationships: https://www.youtube.com/watch?v=IstAk982ntA  
Many-to-Many Relationships: https://www.youtube.com/watch?v=7D8u6Lb2BKU  


Caspio also has training materials that can help you in building your applications.

You may want to visit them: 






Link to comment
Share on other sites

  • 0


Just want to add to the previous comments above, the first thing that you need to do is to build a normalized and well-architectured table.  And for you to know the fields and tables that you need, you need to define the workflow of your application.  As well as the Level of Users of the app. In this manner, it would be easy for you to identify which tables that you will need, and what type of relationship you need to establish.

By the way, they offer free instructor-led training sessions multiple times per week. These online training helps you get up and running quickly. You can sign up in these training session here: http://howto.caspio.com/pre-recorded-live-training/ or watch the pre-recorded training sessions at http://howto.caspio.com/pre-recorded-live-training/  

Those online training really helped me a lot in building my desired application.  I hope that it will help you too.


Link to comment
Share on other sites

  • 0

Here are a few quick tips in getting started that I use for new apps:

Key areas to scope prior to beginning and as you progress:

  1. What entities (tables) are needed, and general purpose of each.
    • Define what data you need for each, and what type of data this is
  2. What users and roles will be needed to access this application?
    • Who is using the app. Group them into roles and permissions for each role/sub-role
  3. For each user/role, what permissions should they have on each entity.
    • What should each user role be able to do with each set of data. Keep this simple: Insert, Edit/Delete, View only.  
    • Should this be for the whole data-set, or just a sub-set. How is sub-set determined?

I use a table like the screenshot below to help build this out:


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...