Hello Jeff
We are doing both options. we have a couple of projects running in the same configuration and another couple of projects where we share an analysis.
The shared config works well, there are only a couple of small issues.
One app goes out without including any dll's in the exe and the other does and with a shared config, Windev gets confused and so each time we compile we have to go through all the config items and set up the framework for each app as we go.
There is a time delay when you switch between the two configs as it recompiles and at least once a week we delete the cpl directory - just in case.
There will be more compiler error messages as it tries to cope with what it thinks is missing
e.g if you share any windows between the two configs and then they branch out and run other windows that are not included in both, the compiler thinks that there are missing items.
The apps we run off a shared analysis occurred because we did not want to change versions on an existing V12 app and started on a new app in WindevMobile 14. This all works fine with no problems. We don't use any classes so we just imported the global procs that we needed.
There is a point in favour of just sharing an analysis and not using shared config. With a shared config, all apps in that config must run with the same version of Windev but with a shared analysis they can be whatever version is required and this makes it easier to maintain as you don't need to re-release all apps at the same time. I maintain the shared analysis using the lowest Windev version in case there are any backward incompatibilities.
Regards
Al