CaseTalk has stored its roaming configuration in %APPDATA%\CaseTalk12 ever since version 12. The folder name was derived from a compile-time constant that was never advanced past 12, so versions 13, 14 and 15 all share the same CaseTalk12 folder.

Why this matters:

• Running an older and a newer CaseTalk side by side is unsafe: they read and write the same settings, styles, keys and caches.
• Upgrading can leave the shared folder in a state an older version no longer understands.

Change (in progress for 15.0):

• The program version is now read at runtime from the application's own version information, so the profile folder follows the real major version (e.g. %APPDATA%\CaseTalk15).
• On first run of a new version, the files from the most recent previous version folder are copied forward into the new one, while the old folder is left untouched - so older versions keep working from their own profile.
• Scope: one folder per major version (CaseTalk15, CaseTalk16, ...). Portable installations are unchanged: they already keep their data next to the executable.

Still to do (tracked here):

• A few subsystems still write to a hard-coded CaseTalk12 location (crash reports, diagnostic logs, the database setup helper's CaseTalkManager.ini). These should follow the versioned folder.
• The installer still deploys default style/config files to {userappdata}\CaseTalk12; it should target the versioned folder (or rely on the app's first-run copy-forward).