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
Can you tell me what issues you've encountered with apps containing 40+ tables? If QuickBase can handle it, I'm game, but I am leary of a monolithic app, with logic becoming so complex that you can't fix anything without breaking everything else.
On the other hand, I'm not trying to add undue complexity to my life. If the multiple-app-structure is more expensive and less useful, than I'll take my chances with the monolith.
I'm just trying to understand the abilities of QuickBase and the ramifications of my decisions before I commit to them, but I'm (of course) in a hurry to get in and complete some objectives.
Thanks,
~Rob
On the other hand, I'm not trying to add undue complexity to my life. If the multiple-app-structure is more expensive and less useful, than I'll take my chances with the monolith.
I'm just trying to understand the abilities of QuickBase and the ramifications of my decisions before I commit to them, but I'm (of course) in a hurry to get in and complete some objectives.
Thanks,
~Rob