Toad World® Forums

Uninstall Toad Data point leaves connections and tasks


#1

Hi,
We are running Toad Data Point 3.3.0.1526 on Windows 7. We wanted to do an uninstall to remove everything related to Toad Data Point, and then do a clean install. The uninstall and reinstall ran fine. However the Connections re-appeared, as well as all the tasks. Is there a way to remove everything, so it’s a clean re-install?


#2

Files that contain connections, application layout, settings, etc are kept in the user profile\AppData\Roaming\Quest Software\Product name and version. There is a link from the Help | about window name App Data dir. Here is an example

C:\Users\dpeabody\AppData\Roaming\Quest Software\Toad Data Point 4.3

When you uninstall only the files from the original install are deleted. The files mentioned above are generated during the run of the application. When a user installs a new version of the product we automatically migrate these files to make it easier for the user to continue using the product.

To completely remove the files you will need to do manually or with a bat file.

P.S. It is really a great convenience to retain the connections, etc between releases. Why do you want to delete them?


#3

Thanks for the info Debbie!.

I’ve left them for now.

We wanted to delete them, as we were having serious issues with Toad Submitting Scheduled jobs. Here’s a summary of what happened:

  1. We had to change our connection ID and password. It was for an ODBC connection to an iSERIES.

  2. We changed the connection ID and pwd and then opened each .tas and manually refreshed/re-selected the connection ID on each SQL that the .tas ran & re-saved them.

  3. We ended up having to cancel one of the .tas jobs. We cancelled it in iSeries and in TOAD. As cancelling the TOAD .rtas, does not cancel the job in iSERIES.

  4. After that, whenever TOAD submitted a scheduled job, it submitted the wrong job. It submitted the job of the one we cancelled at #3.

We decided to uninstall TOAD, and re-install it. After the re-install, we saw all the scheduled jobs come back. So we deleted and re-added the scheduled jobs. Everything seems ok now.

Steve Biggs

Senior Business Analyst, Business Solutions

T 613.634.9984 ext. 4189484

C 613.331.4934

Submit a VPS Intake Request

cid:image006.png@01D185B9.12E9EF20


#4

I assume you are using the job scheduler to schedule these jobs. Here are some points to know.

  1. Connect info is not embedded in the automation script. Connections are looked up from the automation script in the connection manager and used. (Connections.xml in App Data Dir for that version of TDP)

  2. When you schedule a job you tell the windows task manager to run x*.tas file with TDP X.X and it uses the connection files for the version from the add data dir.

  3. So when you upgrade versions of TDP you would need to do the following things to sync all of this up.
    a) When starting up the new TDP chose to migrate the settings. This will copy over your connections.
    b) There is a window on first start that shows you all of your TDP automation scripts that were run on older versions and asked you if you want us to programmaticly change the schedule to run with the new version. To sync them up you should say yes.

Hope that makes sense. So connections, and what version of TDP is running the script need to be set to what you want. Some people do not upgrade their connections or scripts on first run. They want to test out the new version. You can still do the syncing by exporting and importing your connections (from connection manager) and change the TDP that runs the scripts in the job manager. There is a button on the tool bar.


#5

Thanks Debbie!.

Here’s an example of what happens when we change the connection ID. (I’ve had to mock this up a bit and obscure ID’s), But when we change the ODBC Connection ID, the SQL’s retain the ID of the previous ID that was used when the .tas was built. The only way we found to fix it was to open each .tas, and click on each SQl within the tas, and select the new ID.

Steve Biggs

Senior Business Analyst, Business Solutions

T 613.634.9984 ext. 4189484

C 613.331.4934

Submit a VPS Intake Request

cid:image006.png@01D185B9.12E9EF20


#6

I see. We don’t currently have a way to change connections within a script. When i run into this I tend to open *.tas file as xml and find and replace. There is a nice feature in TDP for locating multiple files to find and replace items such as this. Open an editor and in the Edit menu there is a find and replace in files. You can configure it to look in a specific dir and subdirs to locate files that have your string in the content of the file. You can do a replace or open them separate in editors and manually replace the strings. findall


#7

Ok, thank you! Have a great holiday!

Steve Biggs

Senior Business Analyst, Business Solutions

T 613.634.9984 ext. 4189484

C 613.331.4934

Submit a VPS Intake Request

cid:image006.png@01D185B9.12E9EF20