ContributionsMost RecentMost LikesSolutionsRe: Need Special Scheduling Report HelpThis type of form is possible to create. I'd love to discuss this with you. bowencl5157@gmail.comRe: Formula Duration in a nested if statementProblem: If([Appraisal Received]=true, (ToDays(([Appraisal Due Date]-[Appraisal Received Date])))) ------------------------------------------- Solution: Because the desired result is a rich text, the best route would be to create a formula - Rich Text field. It's also best to define variables to separate and define the segments of the argument. Also, a solution to get a red background with white font would be to use a <p> tag with style attribute and concatenate into the formula. Try the following: ------------------------------------------- Var Duration Days = ToDays([Appraisal Due Date]-[Appraisal Received Date]); Var text Output1 = ToText($Days); If($Days <= 0, "ON TIME", "<p style='background-color:red;color:white'>"+$Output1+"</p>"); --------- this may not work initially due to some possible syntax errors but this should point you in the right direction.Re: Is is possible to send notifications based on summary fields in parent records?Quickbase needs to add the ability to send notifications based on formulas not just user activity. The platform is too expensive not to have this functionality.Re: 40 Level Markup TableA suggestion would be to have 2 tables: Table 1: Purchases Table 2: Items Set up 1 relationship: 1 purchase to many Items In the Items table, create a field called cost. In the relationship table, create a summary field called total cost. In the purchases table, create a formula-number field called markup with the following formula: If(([Total cost]/50)<1,0, If(([Total cost]/50)>=1,[Total cost]/50)) the "[Total cost]/50))" section would be based on the what you'd prefer to increment by. for example: If you'd prefer to have a markup of 50% for every 50 dollars, it would be ([Total cost]/50)*.5 You'd use this instead: If(([Total cost]/50)<1,0, If(([Total cost]/50)>=1,([Total cost]/50)*.5)) In the purchase table, create a formula-number field called final price with the following formula: [markup]+[Total cost] Now, you'd be able to add multiple items to a purchase and apply a markup to the total amount when the total amount reaches a limit. Without the 40 lined case formula, you'd loose the ability to control each level individually.Re: I am trying to build a project relationship which involves subcontractors, assigned subcontractors and subcontractor contactsThe best solutions would be to setup 2 relationships: Relationship 1: (between Projects and Sub-Contractor's Tables) 1 Project - Many Sub-Contractor Assignments, Relationship 2: (between Sub-Contractor's and Contacts Tables) 1 Sub-Contractor - Many Contacts This will allow you to select multiple Sub-Contractor(s) for 1 project and multiple Contacts for 1 Sub-Contractor.Re: I am trying to build a project relationship which involves subcontractors, assigned subcontractors and subcontractor contactsThere are an endless number of solutions. The basic concept is to make sure that the tables that you are looking to reference from your main table are on the "one" side of your "one-many" relationships. There also has to be a field on the main report that matches the key field on the reference table. Also, ensure that the key field on the reference table is unique. If your main table is projects and your looking to reference contractors, ensure that contractors are referenced on your projects table in a common field. Example: Projects Table - record 1 Project(field): A Contractor(field): 1<-- "this would be the common field" Contractors Table- record 1 Contractor (field): 1(key field)<-- Name(field): John Smith 1 Contractor - Many Projects Key field(Contractor) Now you can bring over "look-up" fields to the Projects table from the Contractors table that reference the contractors. Projects Table - record 1 Project (field): A Contractor (field): 1 Related Projects (field): 1 Contractors - Name: John SmithRe: I am trying to build a project relationship which involves subcontractors, assigned subcontractors and subcontractor contacts1. Its best to create a table for each category (Contractors, Sub-Contractors, Contacts). 2. Make sure each table has a key field that is unique. 3. Decide which table will be your main table. This table will be on the many side of you "one-many" relationships. For example: if projects is your main table, your first relationship would be a "1-project to many-contractor", "1-project to many-Sub contractor", and a "1-contractor to many-contacts"relationship. The parent would be able to write to the child and allow you to add more than one contact.Re: Logging Changes in a field breaks a formula. How can I log the changes and keep the formula?QuickBase should have better articles. This article does not help us at all.