You'd probably want to 'replace' the address fields in Projects with Lookup fields from the parent Customer table.
Do you know how to bring Lookup fields into a child table from a parent table?
You would want to open the table to table relationship interface. Click on any of the two tables' tab at the top of your application. Click the Settings link at the top left lying just underneath the HOME button.
On the Settings page, click on Table to Table Relationships.
On the next page, under the Relationship column, click the table pair to modify. It will probably be declared as, Customer >> to >> Projects.
In the relationship interface for these two tables, on the right-hand side is the child. There is a button at the bottom of the child column, "Add Lookup fields". Click this button.
On the page that follows, you're able to select up to three Parent fields at one time to be brought over into the child table. Select the Address fields.
The ADDRESS Data Type:
You did mention wanting to use Google maps and so therefore, you want to be sure you have in the Customer table the Address data type for your address fields.
The Address data type is broken up into six parts by QuickBase. [Address Field Name]: City; [Address Field Name]: Country; [Address Field Name]: Postal Code; [Address Field Name]: State/Region; [Address Field Name]: Street 1; [Address Field Name]: Street 2.
You'd have to import into each of these as separate columns of data if you do not already have this data type established.
Let us know where you are so far.
Yes, Project is child to Customers. Your provided screen shot is the evidence of that. Are we certain that all the Address components are all populated in the Customer records?
When you click into the address lookup portion of the Address data field ( the first text area that has a magnifying glass at its far right ) Google will take what is typed in there and populate the Address field components. If Google does not populate that, you do not need to either.
I have created the association in a test database with the Address data type and bringing in 1 to 3 lookup fields -- components of the Address field data type -- and it was successful.
I'd like to suggest deleting the lookup fields from the child table and bring in the Address data type components as lookups again.
Be certain that you are using the Address data type in Customers for the address information, and not just regular text fields.
You can use just the one main Address field component as a test of this effort, the one that does the Google search.
I feel that you may have some junk lookup fields in the child table. Click the + sign next to the lookup field and see if there is an associated Related Customer Address field that goes with it.