I think the problem is that you used the standard new button instead of a custom one. Because in that situation you have a new company but not a new address and hence you can not edit it. Instead of the standard new button create a custom one where you create a new company object and a new address object. Make sure that you set the reference in this microflow and as a last action show the new/edit page of company.
If you are sure both entities are created correctly, check if the access rules are set correct for the role of the user you are testing with. Also there is a setting on the dataview of the address where you can set the editable state.
I hope this helps.
Presumably there is a reason to have a separate Address entity, like it is used in other places as well as company. One way to approach this is to make your Company entity a specialization of the Address entity - that way all the address fields are part of the Company record, but you can also use address by itself without the company associated with it.
To do this, open the Company entity in the Modeler and choose the Address entity as Generalization on the properties.
What Ronald says, but you could approach this using an ON CREATE MF related to the New-action for Company.
Here is a sample application you can download (created in 6.2.0) which shows how this works with a custom New button instead of the standard one