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
This sounds like 1 app to me with many tables and relationships. I have apps with 50 tables. If the app is basically doing one function which is highly integrated and the users are all doing a part if that integrated process, then I suggest 1app.
While you can have what are called cross app relationships, meaning that one app can look up data from another apps table, typically you would only do that when the other app is really doing a separate function, but you corrrectly don't want to manually duplicate information like a customer list or item list.
While you can have what are called cross app relationships, meaning that one app can look up data from another apps table, typically you would only do that when the other app is really doing a separate function, but you corrrectly don't want to manually duplicate information like a customer list or item list.