Hi Geert,
That makes sense. Toad checks its Team Coding settings when it makes a connection to the database; so if you have both versions already connected, you'd need to disconnect the other session and reconnect in order to read Team Coding's configuration.
But, when i changed a few options, adding procedures for a few schemes , and press OK, my project is corrupt.
This could be related to the same issue listed here:
This was an issue found within the data access component we use to connect to Oracle. This affected only reading of LOB values, rather than the data that's actually stored in the table. If you look at the same column value in Toad 14.0, is it also corrupt in there? My suspicion is that it will probably look completely fine. This issue has been addressed in Toad 14.2 Beta.
Give that a try and let us know what you find.
Thanks,
-John