We are going from 2022.0.0.1892 (A) to 2022.1.0.2819 (B)
I am a bit confused about runtime version setting on system options level vs. runtime version setting on project level.
After upgrade I can compile the combinations B/A and B/B but not A/A. The latter releases a cycling error message relating to DB connections, which forces hundreds of response clicks to get through without crashing the workspace.
Now B/A will be fine if the deployed EXE and PBD files then become compatible with the existing client work stations which all have runtime components from the previous version (A). Is this correctly understood?
I should add that we normally push exe/pbd files to a fileserver available to the clients for each build of our applications, while the bulk of the runtime components are copied to each client once/twice a year as we upgrade from one version of PB to the next. I want to postpone this latter operation in the hope that the B/A (or should it be A/A?) combination on the developer stations will be compatible with the existing client runtime components(A).