How do I keep this error from popping up every time I make a connection?
Output: The Team Coding Support Version is not current, and is not fully compapatible with this release of TOAD. A Database Adminstrator must run ‘Upgrade Team Coding’ in Team Coding Configuration. (Dbl. click for more info.)
Thread created by jdean
How do I keep this error from popping up every time I make a connection?
Output: The Team Coding Support Version is not current, and is not fully compapatible with this release of TOAD. A Database Adminstrator must run 'Upgrade Team Coding' in Team Coding Configuration. (Dbl. click for more info.)
I have the same problem. Team coding is disabled and everything in the options under Source Control is unchecked and the default VCS is set to . TOAD still insists on checking for a proper configuration. Maybe my needs to be configured.
To hide the message on startup there is an option in Toad Options – Source Control - Team Coding – Hide Start up messages. (Toad 12 or higher)
It looks like there is an issue with some of the Team Coding objects being removed.
Assuming that Team Coding is installed in the Toad Schema ( or whichever schema you use for server side objects). Check the Toad Schema or the schema where
Team Coding is installed for these tables. If any are missing this may be the issue.
Also check for the PUBLIC SYNONYM
QUEST_COM_TEAM_CODING
FOR TOAD.TC_CONFIG .
If this is missing or pointing to an invalid table this could be the issue.
Team Coding was installed with a version of Toad 10.6 or lower. I have tested this by installing Team Coding in Toad 10.6 and running in toad 12.0 and do not
get the Table not found error you describe. When I open the Team coding Configuration window, the Upgrade Team Coding button is enabled. To uninstall , you must first run the upgrade first. You will then be able to run the uninstall.
Alternatively, you can run the attached script which was generated by Toad 10.6.
Team Coding was completely rewritten a while ago (after the original post in this thread). As a result, this option no longer exists. Are you receiving the message in the original post when you log into a database or perhaps a different message when logging into a database?