ContributionsMost RecentMost LikesSolutionsRe: Creating Notes Table for CRM and ContactsGot it, that works. Yes in part that was the question. Plus just making sure that the relationships and number of records would not be an issue.Re: Creating Notes Table for CRM and ContactsOkay, thanks! So is my logic appropriate? One master table of notes and relations to each table that I want a user to be able to add a "note" to? The only thing that is a struggle on that is I see on the forms it creates a "subtable" and they have to open the notes. I was more or less hoping to be able to create an experience where the user can read them inline. Much like the way we are communicating on this forum. I can types notes directly, save them, and users read them and see who posted them and when.Re: Creating Notes Table for CRM and ContactsSure.... So currently it as attached. Keep in mind this app is in its infancy so much of it is not developed yet. My thought and understanding is that the Notes table should stand alone and through the relationships it "inherently" has a relationship with companies, contacts, and projects because of the link to opportunities. So I can see the notes on any of those related tables. But my other concern is at some point that Notes table is going to get massive with tens of thousands of records. I also thought I would relate contacts and companies and projects to notes. This way if I need a note related to a person but not a specific opportunity I am able to do that. So if the related opportunity field is blank, it would not pull that note for an opportunity. I am just nervous as I continue to add more relationships to this note table (because I want to ultimately add a note on anything) all of these relationships are going to be very ineffective from a database speed side. Re: Newbie looking for help on the best application architecture for a complex appOh wow this is a great point and might point me in another direction. I do want different users to have different initial views. So I cannot configure it based on role? It is based on app? For example I want all users to see their tasks throughout the entire system, but I want Project Managers to see Project Status on their home page, Sales team to see sales pipeline and opportunities, designers to see project status for what they are working on etc. I cannot create different dashboards based on roles? Thanks again for the help, this is really great for getting started!Re: Newbie looking for help on the best application architecture for a complex appAustin, so I did read this thread and it didnt quite help me all the way through. The downside of cross application data I can see is managing the security as well as navigation. I would think a single app is better in that regard. However, the complexity of developing a single app will certainly be significant. Are there any resources to speak to the downsides of a single large application? We currently have 50 employees so for hte foreseeable future I cannot see us being concerned with 100+ employees. Of course that could happen one day. But I am not sure how taxing we really would be on a single application system. Just not sure how to gauge that.Re: Newbie looking for help on the best application architecture for a complex appThanks Chayce, I really do buy into the simplicity of future development if nothing else. For example one major component of the app is going to be to maintain a database of contacts, the contact manager. That seems to me like it would be a fairly simple system to quickly build out and keeping it isolated could be a real benefit. I noticed your quick base sync note.... Would I need to sync data or can I just reference tables across apps? Just wanted to ensure there is no significant performance loss in doing that. It seems like that would work well on my end but not sure if that creates security issues or otherwise.Newbie looking for help on the best application architecture for a complex appHello, I am very new to Quick Base and playing with the trial. While under the trial I am most certainly not going to fully develop this app, but my hope is that I can find a platform in a way to make an ERP system for my company. Basically a hybrid of an architectural firm and contractor in one so we need to manage projects from design through opening day. Many phases, many deliverables, etc. One of my goals is to take what is now independent systems and combine into one: Project Management Software CRM Expense Tracking Communication Tools File Storage (for project related material) Etc. So my question is do I develop all of this one application or will that be cumbersome? Should i build a Contact Manager App, an Opportunity Manager App, a Project Management App and share data or build all under one master application? The architecture of Quick Base seams to support individual apps, but most people through forum seem to say one big app. Currently we are 50 employees and expecting to go through a nice growth period. But we have a long time until we are in the hundreds count (although certainly hope to get their one day!) Thanks in advance