QuickBase Architecture Considerations
So, I'm new to QuickBase, and I'm trying to understand the true intent of this 'codeless' application. I have a complex set of data interactions that I must control, and I'm wondering if I should...
Forum Discussion
In my experience It is much easier and easier to maintain in one application. When you have things in different apps, you have to have the users in all apps, and generally speaking it makes it harder to keep track of.
I've built apps that have 40+ tables for very complex workflows and information.
I'm curious, what is your use case or industry that you are trying to solve this for?
I've built apps that have 40+ tables for very complex workflows and information.
I'm curious, what is your use case or industry that you are trying to solve this for?
My company is a non-profit organization that has members located throughout my state. These groups (roughly 2000) are organized in a variety of ways. One primary aspect of my app or apps will be to organize these groups and their constituents and properties in an easily accessible way to my group's employees or other internal actors.
The other primary concern involves the variety of stakeholders we interact with in order to conduct business. These groups (roughly 20) all have initiatives they require we meet in order to satisfy their concerns. We represent our ability to meet these requirements through a variety of reports that track our involvement with our member groups. Many of these objectives are redundant, but all stakeholders have their own scope or perspective concerning the work we do, i.e. - 'Create Jobs', 'Educate', 'Conserve', 'Train', etc.. so our reports must be tailored to any given objective.
So, I have quite a task in front of me, and QuickBase is the tool I was given. I'm new at the moment, but I'm sure if I pull this off, I'll be QuickBase GrandMaster, or whatever similar title they have. :)
I dunno if this helps, but I felt inclined to share.
Thanks again,
~Rob
The other primary concern involves the variety of stakeholders we interact with in order to conduct business. These groups (roughly 20) all have initiatives they require we meet in order to satisfy their concerns. We represent our ability to meet these requirements through a variety of reports that track our involvement with our member groups. Many of these objectives are redundant, but all stakeholders have their own scope or perspective concerning the work we do, i.e. - 'Create Jobs', 'Educate', 'Conserve', 'Train', etc.. so our reports must be tailored to any given objective.
So, I have quite a task in front of me, and QuickBase is the tool I was given. I'm new at the moment, but I'm sure if I pull this off, I'll be QuickBase GrandMaster, or whatever similar title they have. :)
I dunno if this helps, but I felt inclined to share.
Thanks again,
~Rob