Design/ workflow advice for executable
The fundamental question is: is there a workflow to maintain executable, distributed versions of a database. The executable is created from the developer utilities in FMP Advanced (11).
The database has 2 files: the interface (no tables) and the data.
What does one need to establish when either the interface or the data files or both are changed and want to implement those changes in the distributed version? Is there a way to "unbundle" the executable to segregate the interface and data files again?
I am not sure if I've provided enough information. At this point I'm not looking at a lot of distributed files - just home based stuff on other computers here. But, it seems to me that there should be some way to update tables or update the interface on distributed files.
Thanks in advance.