Hi Chris,

That would surprise me, but you might be right? "has allowed us to switch the runtimes during execution" I'm not aware of this. I know you can choose a different runtime when compiling and building your EXE, but no way I've heard you can switch "during execution".

Maybe someone else can confirm this.

regards.

The runtime switch is for the PB IDE, not the compiled application.

Since nobody has indicated why changing version of DLL's to use is a bad idea, I think it's worth a bit of detail to describe it.

A PB EXE is compiled with certain assumptions about it's runtime environment. If an internal call in a new version of the DLL's now returns a long instead of an int, or a range of values instead of a simple 0/1, the compiled EXE can, and will, have problems calling this internal function, and might work flawlessly, until it doesn't. When it crashes, it may not even be related directly to that call and just cause a generic "access violation". Worse than a simple return value change, it could be a pointer that overwrites data, and corrupts it, prior to be written to a database, in which case you'll never know how/what corrupted your data. These types of internal DLL changes can and will exist, and won't be documented by Appeon because they're internal.

As with earlier versions of PB, it's never safe to run your compiled EXE with mismatched DLL's. ALWAYS keep them in sync.