Flowing updates from master front-end copy to all existing, linked user copies?

[TerraEarth]

The database in question is split, the front-end is copied from a directory onto the user's computer.



I have noticed that user's can modify/alter their copy (Add queries, forms, etc) independent of the master copy.

However, is it possible to alter a form that -should be- shared between all copies (i.e. a form that exists in the master front-end copy itself) and have that update flow to all user-copies?

For example, I have a form on a front end that is a simply query for a customers table. If I wanted to change one of the text fields from "Plain Text" to "Rich Text" in the master copy, is there a way to flow this update down to all the preexisting user copies? i.e. if this form field property update took place on 3/14/2019, would it flow to the front-end copies that were copied before that date? If not, is there a way to make it so?

[ssanfu]

No. Design changes will not "flow" to other copies of the FE.
You would have to copy the "New" master FE (after the change) to each of the users computers.

[Micron]

This is a very common topic that you can research for ideas, like

You make a change
User opens db, which causes comparison of version number.
If different, they can't open db but they can manually click shortcut get an update or process can be automatic.
Or a host of variations on the theme, such as nice to have upgrades vs mandatory

[orange]

See this material from DevHut (Daniel Pineault) re front end deployment ideas.
Good luck.

[TerraEarth]

Thanks, I will look into that